https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78529
--- Comment #33 from rguenther at suse dot de ---
On Wed, 22 Mar 2017, jakub at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78529
>
> --- Comment #32 from Jakub Jelinek ---
> It is actually the *-lib.c files that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78529
--- Comment #32 from Jakub Jelinek ---
It is actually the *-lib.c files that should be -fno-lto.
But it seems all the source files are compiled/linked using one driver
invocation, so I have no idea how to do -fno-lto just for one file.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78529
--- Comment #31 from Jakub Jelinek ---
So, is there a way to request -fno-lto compilation of the
gcc.c-torture/execute/builtins/lib/*.c TUs? The rest probably can stay -flto
when testing lto.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78529
--- Comment #30 from Richard Biener ---
Kind of SUSPENDED I guess. Or we need to fix this testsuite part (in the past
we just added more and more flag workarounds).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78529
--- Comment #29 from Jan Hubicka ---
I think the official answer for LTOing symbols implementing runtime (i.e. those
that can be introduced by middle-end) is "don't do that". We may support LTOing
them with an explicit attribute "used" on them
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78529
Richard Biener changed:
What|Removed |Added
CC||hubicka at gcc dot gnu.org,
