On Wed, 2006-04-19 at 12:50 -0700, Philip Brown wrote:
> On Tue, Apr 18, 2006 at 07:50:35PM -0400, Laszlo (Laca) Peter wrote:
> > On Tue, 2006-04-18 at 14:44 -0700, Philip Brown wrote:
> > > Interesting.
> > >
> > > This is not a deliberate thing. Apparently, it's just a side-effect of
> > > using sun compilers with the -fast option.
> >
> > The magic compiler option you need is -xregs=no%frameptr
>
> sounds like that turns OFF frameptr, not re-enables it after -fast
> removes it.
> aha.
>
> -xregs=%frameptr
>
> would seem to be the magic.
No, -fast includes -xregs=frameptr, which corresponds to
-fomit-frame-pointer in gcc. -xregs=no%frameptr turns this
behaviour off:
-xregs=r[,r...] Specify the usage of registers for the
generated code.
r is a comma-separated list of one or more
of the following: [no%]appl, [no%]float,
[no%]frameptr.
[no%]frameptr (x86 only):
[Does not] Allow the compiler to use the
frame-pointer register (%ebp on IA32, %rbp on
AMD64) as an unallocated callee-saves register.
Using this register as an unallocated callee-
saves register may improve program run time.
However, it also reduces the capacity of some
tools, such as the Performance Analyzer and
dtrace, to inspect and follow the stack. This
stack inspection capability is important for
system performance measurement and tuning.
Therefor, using this optimization may improve
local program performance at the expense of
global system performance.
Laca
> Although it does apparently slow down performance.
>
> Is it really so important to have dtrace have extra visibility
> into the openssl shared libs?
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
