This is the mail archive of the gcc@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: -fobey-inline (was Re: gcc and inlining)


> There we're making an explicit tradeoff: using aliasing information allows
> much better code generation but indeed will break certain types of
> badly-written code.  But we warn the user of this possibility and support
> a -fno-strict-aliasing if this is a concern of the user.  But the point is
> that the breakage is not gratuitous: there's a good reason for it.

Indeed, and the argument here is more about what the default should be, rather than
whether -fno-strict-aliasing should be supported (I have not seen anyone argue that
supporting this switch threatens the sanity of gcc developers). Actually we have
found that certain unusual constructions in Ada (in particular forcing scalar
parameters to be passed by reference, which is outside normal Ada semantics, but
possible in GNAT using non-standard pragmas) cause unexpected results which can
be "cured" by -fno-strict-aliasing.


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