public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug lto/50679] New: Linux kernel LTO tracking bug
@ 2011-10-09 13:54 andi-gcc at firstfloor dot org
  2011-10-09 14:07 ` [Bug lto/50679] " ak at gcc dot gnu.org
                   ` (4 more replies)
  0 siblings, 5 replies; 6+ messages in thread
From: andi-gcc at firstfloor dot org @ 2011-10-09 13:54 UTC (permalink / raw)
  To: gcc-bugs

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

             Bug #: 50679
           Summary: Linux kernel LTO tracking bug
    Classification: Unclassified
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: lto
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: andi-gcc@firstfloor.org


Meta bug to track various problems encountered while building the Linux
kernel with LTO


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug lto/50679] Linux kernel LTO tracking bug
  2011-10-09 13:54 [Bug lto/50679] New: Linux kernel LTO tracking bug andi-gcc at firstfloor dot org
@ 2011-10-09 14:07 ` ak at gcc dot gnu.org
  2011-10-09 17:12 ` markus at trippelsdorf dot de
                   ` (3 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: ak at gcc dot gnu.org @ 2011-10-09 14:07 UTC (permalink / raw)
  To: gcc-bugs

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

ak at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hubicka at gcc dot gnu.org

--- Comment #1 from ak at gcc dot gnu.org 2011-10-09 14:06:44 UTC ---
urrently I have to revert 2 patches to get anywhere near a build
and work around 50644. 32bit builds don't work at all because of
the tree-nrv problem.

50620 causes incredly slow builds because partitioning has to be disabled


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug lto/50679] Linux kernel LTO tracking bug
  2011-10-09 13:54 [Bug lto/50679] New: Linux kernel LTO tracking bug andi-gcc at firstfloor dot org
  2011-10-09 14:07 ` [Bug lto/50679] " ak at gcc dot gnu.org
@ 2011-10-09 17:12 ` markus at trippelsdorf dot de
  2012-01-02  4:08 ` [Bug lto/50679] [meta-bug] " pinskia at gcc dot gnu.org
                   ` (2 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: markus at trippelsdorf dot de @ 2011-10-09 17:12 UTC (permalink / raw)
  To: gcc-bugs

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

Markus Trippelsdorf <markus at trippelsdorf dot de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |markus at trippelsdorf dot
                   |                            |de

--- Comment #2 from Markus Trippelsdorf <markus at trippelsdorf dot de> 2011-10-09 17:11:52 UTC ---
I've no problems building the kernel with LTO at the moment,
but I use no modules and a fairly minimal config.

I've seen a few strange segfaults while testing the LTO kernel however.

For example:
screen[1608]: segfault at 7fff42d73e98 ip 000000000040600a sp 00007fff42d73ea0
error 6 in screen[400000+55000]
or
zsh[1643]: segfault at 7f7980eb4000 ip 00007f7981db6cb0 sp 00007fff1f4b6dd8
error 7 in libc-2.14.90.so[7f7981d34000+15f000] 

But I'm not 100% sure, that they're really LTO related.


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug lto/50679] [meta-bug] Linux kernel LTO tracking bug
  2011-10-09 13:54 [Bug lto/50679] New: Linux kernel LTO tracking bug andi-gcc at firstfloor dot org
  2011-10-09 14:07 ` [Bug lto/50679] " ak at gcc dot gnu.org
  2011-10-09 17:12 ` markus at trippelsdorf dot de
@ 2012-01-02  4:08 ` pinskia at gcc dot gnu.org
  2012-06-05 16:11 ` markus at trippelsdorf dot de
  2014-04-07  4:00 ` andi-gcc at firstfloor dot org
  4 siblings, 0 replies; 6+ messages in thread
From: pinskia at gcc dot gnu.org @ 2012-01-02  4:08 UTC (permalink / raw)
  To: gcc-bugs

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


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug lto/50679] [meta-bug] Linux kernel LTO tracking bug
  2011-10-09 13:54 [Bug lto/50679] New: Linux kernel LTO tracking bug andi-gcc at firstfloor dot org
                   ` (2 preceding siblings ...)
  2012-01-02  4:08 ` [Bug lto/50679] [meta-bug] " pinskia at gcc dot gnu.org
@ 2012-06-05 16:11 ` markus at trippelsdorf dot de
  2014-04-07  4:00 ` andi-gcc at firstfloor dot org
  4 siblings, 0 replies; 6+ messages in thread
From: markus at trippelsdorf dot de @ 2012-06-05 16:11 UTC (permalink / raw)
  To: gcc-bugs

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 000000000040600a sp 00007fff42d73ea0
> error 6 in screen[400000+55000]
> or
> zsh[1643]: segfault at 7f7980eb4000 ip 00007f7981db6cb0 sp 00007fff1f4b6dd8
> 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.


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug lto/50679] [meta-bug] Linux kernel LTO tracking bug
  2011-10-09 13:54 [Bug lto/50679] New: Linux kernel LTO tracking bug andi-gcc at firstfloor dot org
                   ` (3 preceding siblings ...)
  2012-06-05 16:11 ` markus at trippelsdorf dot de
@ 2014-04-07  4:00 ` andi-gcc at firstfloor dot org
  4 siblings, 0 replies; 6+ messages in thread
From: andi-gcc at firstfloor dot org @ 2014-04-07  4:00 UTC (permalink / raw)
  To: gcc-bugs

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+


^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2014-04-07  4:00 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-10-09 13:54 [Bug lto/50679] New: Linux kernel LTO tracking bug andi-gcc at firstfloor dot org
2011-10-09 14:07 ` [Bug lto/50679] " ak at gcc dot gnu.org
2011-10-09 17:12 ` markus at trippelsdorf dot de
2012-01-02  4:08 ` [Bug lto/50679] [meta-bug] " pinskia at gcc dot gnu.org
2012-06-05 16:11 ` markus at trippelsdorf dot de
2014-04-07  4:00 ` andi-gcc at firstfloor dot org

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).