public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/62077] --with-build-config=bootstrap-lto fails, Date: Tue, 12 Aug 2014 12:51:00 -0000 [thread overview] Message-ID: <bug-62077-4-fRz3uJ0G0o@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-62077-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62077 --- Comment #16 from Richard Biener <rguenth at gcc dot gnu.org> --- Ok, so what happens is that for build/genconfig.o we in one case write a STRING_CST with a const char[7] with itself as main-variant and in the other case with char[7] as main-variant. The STRING_CST is written from ipa_write_jump_function 4237 case IPA_JF_CONST: 4238 gcc_assert ( 4239 EXPR_LOCATION (jump_func->value.constant.value) == UNKNOWN_LOCATION); 4240 stream_write_tree (ob, jump_func->value.constant.value, true); 4241 break; as &"#endif"[0] Its type main variant is built in c-family/c-common.c:1021 and the literal itself in builtins.c:13383. And we indeed get differences in inline_param2 (min size), otherwise no visible differences anywhere in dumps. Not sure how that can explain the type difference for the jump function though... Again, this is build/genconfig.o as compiled by stage1 cc1plus vs. stage2 cc1plus (so faster to reproduce / bisect).
next prev parent reply other threads:[~2014-08-12 12:51 UTC|newest] Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-08-09 20:55 [Bug bootstrap/62077] New: " sven.c.dack at virginmedia dot com 2014-08-10 15:41 ` [Bug bootstrap/62077] " sven.c.dack at virginmedia dot com 2014-08-10 15:46 ` sven.c.dack at virginmedia dot com 2014-08-11 8:51 ` rguenth at gcc dot gnu.org 2014-08-11 10:07 ` rguenth at gcc dot gnu.org 2014-08-11 10:19 ` venkataramanan.kumar at amd dot com 2014-08-12 7:24 ` sven.c.dack at virginmedia dot com 2014-08-12 7:47 ` sven.c.dack at virginmedia dot com 2014-08-12 8:03 ` pinskia at gcc dot gnu.org 2014-08-12 8:10 ` rguenther at suse dot de 2014-08-12 8:23 ` venkataramanan.kumar at amd dot com 2014-08-12 9:20 ` rguenth at gcc dot gnu.org 2014-08-12 10:52 ` venkataramanan.kumar at amd dot com 2014-08-12 11:07 ` sven.c.dack at virginmedia dot com 2014-08-12 12:51 ` rguenth at gcc dot gnu.org [this message] 2014-08-13 8:06 ` [Bug bootstrap/62077] --with-build-config=bootstrap-lto fails sven.c.dack at virginmedia dot com 2014-08-13 8:18 ` sven.c.dack at virginmedia dot com 2014-08-13 9:25 ` rguenth at gcc dot gnu.org 2014-08-13 9:57 ` rguenth at gcc dot gnu.org 2014-08-13 10:00 ` venkataramanan.kumar at amd dot com 2014-08-13 11:05 ` rguenth at gcc dot gnu.org 2014-08-13 11:12 ` rguenth at gcc dot gnu.org 2014-08-13 11:21 ` rguenth at gcc dot gnu.org 2014-08-13 12:34 ` rguenth at gcc dot gnu.org 2014-08-13 13:51 ` rguenth at gcc dot gnu.org 2014-08-13 14:02 ` sven.c.dack at virginmedia dot com 2014-08-13 15:09 ` venkataramanan.kumar at amd dot com 2014-08-13 19:43 ` venkataramanan.kumar at amd dot com 2014-08-14 7:26 ` venkataramanan.kumar at amd dot com 2014-08-14 8:45 ` rguenth at gcc dot gnu.org 2014-08-14 10:30 ` rguenth at gcc dot gnu.org 2014-08-14 12:36 ` venkataramanan.kumar at amd dot com 2014-08-14 17:48 ` sven.c.dack at virginmedia dot com 2014-08-14 22:49 ` sven.c.dack at virginmedia dot com 2014-08-15 5:38 ` sven.c.dack at virginmedia dot com 2014-08-15 10:22 ` sven.c.dack at virginmedia dot com 2014-08-15 10:26 ` rguenther at suse dot de 2014-08-15 10:44 ` trippels at gcc dot gnu.org 2014-08-15 10:56 ` sven.c.dack at virginmedia dot com 2014-08-15 11:37 ` trippels at gcc dot gnu.org 2014-08-15 17:28 ` jason at gcc dot gnu.org 2014-08-15 20:02 ` sven.c.dack at virginmedia dot com 2014-08-15 20:07 ` sven.c.dack at virginmedia dot com 2014-08-17 8:19 ` sven.c.dack at virginmedia dot com 2014-08-17 10:55 ` sven.c.dack at virginmedia dot com 2014-08-17 15:49 ` sven.c.dack at virginmedia dot com 2014-08-18 11:00 ` venkataramanan.kumar at amd dot com 2014-08-18 13:11 ` rguenther at suse dot de 2014-08-18 13:36 ` venkataramanan.kumar at amd dot com 2014-08-18 13:40 ` rguenther at suse dot de 2014-08-18 15:03 ` sven.c.dack at virginmedia dot com 2015-04-15 7:30 ` rguenth at gcc dot gnu.org 2015-04-15 7:49 ` vekumar at gcc dot gnu.org 2015-04-15 8:12 ` rguenther at suse dot de 2015-04-15 8:34 ` rguenth at gcc dot gnu.org 2015-04-17 11:04 ` jakub at gcc dot gnu.org 2015-04-17 11:28 ` rguenth at gcc dot gnu.org 2015-04-17 17:10 ` jakub at gcc dot gnu.org 2015-04-17 17:11 ` jakub at gcc dot gnu.org 2015-05-06 14:47 ` hjl.tools at gmail dot com
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-62077-4-fRz3uJ0G0o@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).