[Bug lto/50679] [meta-bug] Linux kernel LTO tracking bug

[rguenth at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50679
Bug 50679 depends on bug 50639, which changed state.

Bug 50639 Summary: -flto=jobserver broken on large LTO build
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50639

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

[Bug lto/50679] [meta-bug] Linux kernel LTO tracking bug

[andi-gcc at firstfloor dot org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50679

Andi Kleen andi-gcc at firstfloor dot org changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #4 from Andi Kleen andi-gcc at firstfloor dot org ---
No open bugs for kernel LTO in 4.8+

[Bug lto/50679] [meta-bug] Linux kernel LTO tracking bug

[markus at trippelsdorf dot de]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50679

--- Comment #3 from Markus Trippelsdorf markus at trippelsdorf dot de 
2012-06-05 16:11:05 UTC ---
(In reply to comment #2)
 I've seen a few strange segfaults while testing the LTO kernel however.
 
 For example:
 screen[1608]: segfault at 7fff42d73e98 ip 0040600a sp 7fff42d73ea0
 error 6 in screen[40+55000]
 or
 zsh[1643]: segfault at 7f7980eb4000 ip 7f7981db6cb0 sp 7fff1f4b6dd8
 error 7 in libc-2.14.90.so[7f7981d34000+15f000] 
 
 But I'm not 100% sure, that they're really LTO related.

No. It turned out that the segfaults above weren't related to LTO kernels.

[Bug lto/50679] [meta-bug] Linux kernel LTO tracking bug

[pinskia at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50679

Andrew Pinski pinskia at gcc dot gnu.org changed:

   What|Removed |Added

   Keywords||meta-bug
 Status|UNCONFIRMED |NEW
   Last reconfirmed||2012-01-02
Summary|Linux kernel LTO tracking   |[meta-bug] Linux kernel LTO
   |bug |tracking bug
 Ever Confirmed|0   |1