This is the mail archive of the gcc-bugs@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]

[Bug lto/55102] The options -flto and -On do not behave as described in GCC docs


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55102

Eric Gallager <egallager at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |egallager at gcc dot gnu.org
         Resolution|---                         |FIXED

--- Comment #8 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to rguenther@suse.de from comment #7)
> On Thu, 15 Nov 2018, sandra at gcc dot gnu.org wrote:
> 
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55102
> > 
> > sandra at gcc dot gnu.org changed:
> > 
> >            What    |Removed                     |Added
> > ----------------------------------------------------------------------------
> >                  CC|                            |sandra at gcc dot gnu.org
> > 
> > --- Comment #6 from sandra at gcc dot gnu.org ---
> > I've checked in a patch on trunk to replace the bad example with the
> > explanation in Comment 1, suitably translated into user-speak.  However, in
> > subsequent comments this issue wandered off into discussion of enabling IPA
> > automatically with -flto and other related code changes.  Is the issue
> > adequately resolved just by the documentation change, or do we want to keep it
> > open to track the requested code changes?
> 
> Let's close it.

OK.

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