public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin.liska at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/57483] New: Linux kernel (lto-3.9 branch) compilation fails with enabled LTO
Date: Fri, 31 May 2013 12:41:00 -0000	[thread overview]
Message-ID: <bug-57483-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 57483
           Summary: Linux kernel (lto-3.9 branch) compilation fails with
                    enabled LTO
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: marxin.liska at gmail dot com

Andi Kleen is maintaining Linux kernel LTO branch:
https://github.com/andikleen/linux-misc

Repository version:
5c1e0bc49249c3ff44849a8f72e6cccd1486f38f

GCC used to be able to compile such kernel, regression was introduced in
revision: 198741

Error:
In function ‘alloc_iommu’:
lto1: internal compiler error: in input_gimple_stmt, at
gimple-streamer-in.c:287
0xc76db5 input_gimple_stmt
    ../../gcc/gimple-streamer-in.c:286
0xc76db5 input_bb(lto_input_block*, LTO_tags, data_in*, function*, int)
    ../../gcc/gimple-streamer-in.c:345
0x77d1b3 input_function
    ../../gcc/lto-streamer-in.c:887
0x77d1b3 lto_read_body
    ../../gcc/lto-streamer-in.c:1011
0x77d1b3 lto_input_function_body(lto_file_decl_data*, tree_node*, char const*)
    ../../gcc/lto-streamer-in.c:1055
0x4ff322 lto_materialize_function
    ../../gcc/lto/lto.c:226
0x4ff322 materialize_cgraph
    ../../gcc/lto/lto.c:3084
0x506a88 lto_main()
    ../../gcc/lto/lto.c:3348
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.
make[1]: *** [/tmp/ccRWZATW.ltrans8.ltrans.o] Error 1
make[1]: *** Waiting for unfinished jobs....
/tmp/cckatHC0.s: Assembler messages:
/tmp/cckatHC0.s:10068: Error: symbol `__compound_literal.0' is already defined
/tmp/cckatHC0.s:30211: Error: symbol `__compound_literal.0' is already defined
make[1]: *** [/tmp/ccRWZATW.ltrans6.ltrans.o] Error 1
lto-wrapper: make returned 2 exit status
/home/marxin/gcc-jan/libexec/gcc/x86_64-unknown-linux-gnu/4.9.0/ld: lto-wrapper
failed
collect2: error: ld returned 1 exit status
make: *** [vmlinux] Error 1
>From gcc-bugs-return-423585-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 31 13:06:00 2013
Return-Path: <gcc-bugs-return-423585-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24595 invoked by alias); 31 May 2013 13:05:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 24496 invoked by uid 48); 31 May 2013 13:05:49 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/57319] [4.8 Regression]: bogus "defaulted move assignment for ... calls a non-trivial move assignment operator for virtual base ..."
Date: Fri, 31 May 2013 13:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_known_to_work resolution cf_known_to_fail
Message-ID: <bug-57319-4-RhQLtWKtIk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-57319-4@http.gcc.gnu.org/bugzilla/>
References: <bug-57319-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2013-05/txt/msg02258.txt.bz2
Content-length: 541

http://gcc.gnu.org/bugzilla/show_bug.cgi?idW319

Jason Merrill <jason at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
      Known to work|                            |4.8.2
         Resolution|---                         |FIXED
      Known to fail|                            |4.8.1

--- Comment #7 from Jason Merrill <jason at gcc dot gnu.org> ---
Fixed for 4.8.2.


             reply	other threads:[~2013-05-31 12:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-31 12:41 marxin.liska at gmail dot com [this message]
2013-06-18  9:57 ` [Bug lto/57483] " rguenth at gcc dot gnu.org
2013-06-19  0:22 ` marxin.liska at gmail dot com
2013-06-19 10:43 ` rguenth at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-57483-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).