public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "breedlove.matt at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/65559] [5/6 Regression] lto1.exe: internal compiler error: in read_cgraph_and_symbols, at lto/lto.c:2947 Date: Sat, 02 May 2015 04:45:00 -0000 [thread overview] Message-ID: <bug-65559-4-LNZIhuuZQp@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65559-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65559 --- Comment #33 from Matt Breedlove <breedlove.matt at gmail dot com> --- bootstrap-lto fails to build: `isl_union_map_read_from_str' referenced in section `.text' of M:\msys64\tmp\cceOtKWH.ltrans0.ltrans.o: defined in discarded section `.text' of isl_input.o (symbol from plugin) `isl_union_map_read_from_str' referenced in section `.text' of M:\msys64\tmp\cceOtKWH.ltrans0.ltrans.o: defined in discarded section `.text' of isl_input.o (symbol from plugin) `isl_union_map_copy' referenced in section `.text' of M:\msys64\tmp\cceOtKWH.ltrans0.ltrans.o: defined in discarded section ... Replacing the lto-wrapper with the one from my previous build makes these errors disappear. The patch from my previous build was the following: --- gcc-5.1.0/gcc/lto-wrapper.c.orig 2015-05-01 16:38:03.348243300 -0400 +++ gcc-5.1.0/gcc/lto-wrapper.c 2015-05-02 00:30:58.345729900 -0400 @@ -934,7 +934,7 @@ filename[p - argv[i]] = '\0'; file_offset = (off_t) loffset; } - fd = open (argv[i], O_RDONLY); + fd = open (filename, O_RDONLY|O_BINARY); if (fd == -1) { lto_argv[lto_argc++] = argv[i]; Rainer hasn't tested this yet. I'm going to do a full native bootstrap-lto with this, however it was working fine on everything else I compiled. The issue with the last tested patch was archive files with offsets were getting discarded from the build since we were back to not using the parsed archive filename.
next prev parent reply other threads:[~2015-05-02 4:45 UTC|newest] Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-25 17:06 [Bug lto/65559] New: [5 " rainer@emrich-ebersheim.de 2015-03-25 19:03 ` [Bug lto/65559] " ktietz at gcc dot gnu.org 2015-03-25 20:01 ` rainer@emrich-ebersheim.de 2015-03-25 23:52 ` hubicka at gcc dot gnu.org 2015-03-26 11:19 ` rguenth at gcc dot gnu.org 2015-03-31 13:15 ` rguenth at gcc dot gnu.org 2015-04-06 18:38 ` rainer@emrich-ebersheim.de 2015-04-06 20:01 ` hubicka at ucw dot cz 2015-04-06 20:19 ` rainer@emrich-ebersheim.de 2015-04-07 11:13 ` rguenth at gcc dot gnu.org 2015-04-07 12:09 ` rainer@emrich-ebersheim.de 2015-04-07 12:42 ` rguenth at gcc dot gnu.org 2015-04-07 14:35 ` rainer@emrich-ebersheim.de 2015-04-07 14:40 ` rainer@emrich-ebersheim.de 2015-04-08 8:56 ` ktietz at gcc dot gnu.org 2015-04-22 12:02 ` [Bug lto/65559] [5/6 " jakub at gcc dot gnu.org 2015-04-29 20:12 ` daniel.f.starke at freenet dot de 2015-04-29 20:34 ` ktietz at gcc dot gnu.org 2015-04-30 8:56 ` breedlove.matt at gmail dot com 2015-04-30 13:36 ` rainer@emrich-ebersheim.de 2015-04-30 13:45 ` rainer@emrich-ebersheim.de 2015-04-30 13:58 ` ktietz at gcc dot gnu.org 2015-04-30 14:39 ` rguenth at gcc dot gnu.org 2015-04-30 14:44 ` rguenth at gcc dot gnu.org 2015-04-30 15:08 ` rainer@emrich-ebersheim.de 2015-04-30 17:14 ` rainer@emrich-ebersheim.de 2015-04-30 18:08 ` breedlove.matt at gmail dot com 2015-04-30 20:45 ` breedlove.matt at gmail dot com 2015-04-30 21:51 ` rainer@emrich-ebersheim.de 2015-05-01 8:48 ` rainer@emrich-ebersheim.de 2015-05-01 14:26 ` ktietz at gcc dot gnu.org 2015-05-01 20:32 ` breedlove.matt at gmail dot com 2015-05-02 4:45 ` breedlove.matt at gmail dot com [this message] 2015-05-02 11:43 ` rguenth at gcc dot gnu.org 2015-05-04 10:17 ` ktietz at gcc dot gnu.org 2015-05-04 10:24 ` ktietz at gcc dot gnu.org 2015-05-04 10:25 ` ktietz 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-65559-4-LNZIhuuZQp@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: linkBe 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).