public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "joel at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/50878] [4.7 Regression] ARM bootstrap failure on insn-preds.c with error: dominator of 12 should be 6, not 5 Date: Sun, 30 Oct 2011 23:53:00 -0000 [thread overview] Message-ID: <bug-50878-4-m8umWsUP2i@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50878-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50878 Joel Sherrill <joel at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target|arm-linux-gnueabi |arm-linux-gnueabi | |arm-rtems4.11 CC| |joel at gcc dot gnu.org Host| |x86_64-unknown-linux-gnu --- Comment #10 from Joel Sherrill <joel at gcc dot gnu.org> 2011-10-30 23:52:21 UTC --- FWIW I am using a native gcc on x86_64 to build cross *-rtems4.11 targets. gcc (GCC) 4.7.0 20111029 (experimental) I think this is a native issue (x86_64-unknown-linux-gnu) that is showing up on multiple odd situations. I see this compiling arm-rtems4.11 And I think this is the same thing I saw with the native compiler of yesterday's vintage compiling the head of binutils-cvs to target sparc-rtems4.11 /users/joel/test-gcc/binutils-cvs/src/bfd/sunos.c: In function ‘sunos_check_dynamic_reloc’: /users/joel/test-gcc/binutils-cvs/src/bfd/sunos.c:2328:1: error: dominator of 26 should be 20, not 19 /users/joel/test-gcc/binutils-cvs/src/bfd/sunos.c:2328:1: internal compiler error: in verify_dominators, at dominance.c:1041 I can provide preprocessed source if someone needs it.
next prev parent reply other threads:[~2011-10-30 23:53 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-10-26 22:02 [Bug bootstrap/50878] New: " michael.hope at linaro dot org 2011-10-26 22:03 ` [Bug bootstrap/50878] " michael.hope at linaro dot org 2011-10-27 9:21 ` [Bug bootstrap/50878] [4.7 Regression] " rguenth at gcc dot gnu.org 2011-10-27 10:38 ` vries at gcc dot gnu.org 2011-10-27 11:55 ` rguenth at gcc dot gnu.org 2011-10-27 16:34 ` ramana at gcc dot gnu.org 2011-10-27 16:39 ` ramana at gcc dot gnu.org 2011-10-27 16:57 ` ramana at gcc dot gnu.org 2011-10-27 17:04 ` vries at gcc dot gnu.org 2011-10-27 17:07 ` vries at gcc dot gnu.org 2011-10-27 18:34 ` vries at gcc dot gnu.org 2011-10-30 8:22 ` vries at gcc dot gnu.org 2011-10-30 23:53 ` joel at gcc dot gnu.org [this message] 2011-10-31 10:02 ` vries at gcc dot gnu.org 2011-11-01 21:56 ` vries 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-50878-4-m8umWsUP2i@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).