[Bug 1769] sparc64 not using compiler optimizations

[bugzilla-daemon at rtems.org]

https://www.rtems.org/bugzilla/show_bug.cgi?id=1769

--- Comment #4 from Gedare <giddyup44 at yahoo.com> 2011-03-21 12:54:21 CDT ---
(In reply to comment #3)
> (In reply to comment #2)
> > (In reply to comment #1)
> > > I am OK with the -O2 part, but I am not OK with -gstabs.
> > > 
> > > Why do you need -gstabs? -g is supposed to be sufficient.
> > 
> > With -gstabs, I get C source code line matching in my (non-GDB)
> non-GDB  == your personal use-case == not of relevance to the public.
> 
AFAIW, our research group is the current users of the sparc64 port. It runs on
the Simics simulator, which is not GDB and not free (we have academic licensing
to use it).

> > simulator/debugger.  With -g, I do not get source-line matching, only symbols.
> This only means your debugger doesn't grok the default debugging format gcc
> produces, for whatever reasons.
> 
> Could be your debugger is outdated, could be your debugger is malfunctioning,
> could be your debugger is incompatible to gcc's defaults.
> 
> > So it is mostly a matter of convenience.
> Please try using sparc-rtems-gdb (without -gstabs).
Please note, this patch is for the sparc64 target, which is not equivalent to
sparc32==sparc.  I don't think there is a gdb that supports sparc64 binaries
that use the full (privileged) instruction set and RTEMS.

Anyway, I don't care if the -gstabs is changed to -g or even removed entirely.
It is easy enough to change back by hand if debugging or source-code line
debugging are desired.

-- 
Configure bugmail: https://www.rtems.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.