public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "breiten at lexmark dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/38886] New: 4.3.2 ICE move_insn, at haifa-sched.c:1786 Date: Fri, 16 Jan 2009 21:07:00 -0000 [thread overview] Message-ID: <bug-38886-17199@http.gcc.gnu.org/bugzilla/> (raw) Got this one with the attached file when attempting to upgrade to gcc-4.3.2 for powerpc. This compiles fine with 3.4.6. I've captured the preprocessed output and removed everything I could that didn't make the problem disappear. This is from openssl-0.9.8d. The problem required -O2 or -O3 and -fPIC. But this reduced file only fails at -O2. I'll attempt to attach the original preprocessed output as well. -- Summary: 4.3.2 ICE move_insn, at haifa-sched.c:1786 Product: gcc Version: 4.3.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: breiten at lexmark dot com GCC host triplet: i686-pc-linux-gnu GCC target triplet: powerpc-750-linux http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38886
next reply other threads:[~2009-01-16 21:07 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-01-16 21:07 breiten at lexmark dot com [this message] 2009-01-16 21:11 ` [Bug c/38886] " breiten at lexmark dot com 2009-01-16 21:14 ` breiten at lexmark dot com 2009-01-16 23:51 ` [Bug target/38886] [4.3 Regression] " rguenth at gcc dot gnu dot org 2009-01-24 10:28 ` rguenth at gcc dot gnu dot org 2009-03-13 22:56 ` rguenth at gcc dot gnu dot org 2009-04-22 13:25 ` rguenth at gcc dot gnu dot org 2009-04-22 14:29 ` breiten at lexmark dot com 2009-05-14 6:09 ` bje at gcc dot gnu dot org 2009-05-14 6:18 ` bje at gcc dot gnu dot org 2009-06-26 18:06 ` breiten at lexmark dot com 2009-06-26 19:49 ` mikpe at it dot uu dot se 2009-08-04 12:46 ` rguenth at gcc dot gnu dot org 2010-05-22 18:34 ` rguenth at gcc dot gnu dot 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-38886-17199@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).