https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89893
--- Comment #24 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to 康 珊 from comment #23)
> (In reply to Martin Liška from comment #22)
> > (In reply to 康 珊 from comment #21)
> > > All of the experiments were did in according to the build steps I just
> > > gave
> > > to you.
> >
> > I'm sorry, but I would like to know whether you are talking about LTO builds
> > (w/ --enable-lto in configure) or not? You tried both, so I'm curious which
> > have you used?
> It is configured with "--enable-lto" and LDFLAGS="${LDFLAGS} -fno-lto", I'm
> not sure whether lto takes effect or not. Do you need me remove "enable-lto"
> in configure and try the experiments?
Using "--enable-lto" and LDFLAGS="${LDFLAGS} -fno-lto" is wrong. It will use
LTO because one can't stop usage LTO bytecode by linker option. There's no
assembly that linked would be able to link.
