This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: PATCH: [darwin] Always turn on FP_SAVE_INLINE at -O3


Caroline Tice wrote:


The following is a small optimization in the Apple compiler we would like to put into mainline.
It is Darwin-specific. By always making FP_SAVE_INLINE be true at -O3 or higher we
gain a small performance improvement.


This has been tested on an Apple G4 running apple-darwin. It bootstraps and passes
DejaGnu. Is this okay to commit to mainline?

This is a little unusual, a quick scan of targets doesn't show any for which -O3 has different behavior (although there are several that test -O1 vs -O2), but I can't think of any reason why not, so yes, let's give it a try.

In the interest of propagating rumors via this mailing list :-), what
is the general order of magnitude of "small improvement" here?

Stan


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]