public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/63703] [4.9.2 Regression] cc1: internal compiler error: in init_reg_sets, at reginfo.c:178 Date: Sat, 22 Nov 2014 16:54:00 -0000 [thread overview] Message-ID: <bug-63703-4-uY6sqOCLOS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-63703-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63703 Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target|powerpc-unknown-darwin |powerpc-apple-darwin9 Status|UNCONFIRMED |NEW Last reconfirmed| |2014-11-22 CC| |fxcoudert at gcc dot gnu.org Host|powerpc-unknown-darwin |powerpc-apple-darwin9 Summary|[4.9 Regression] cc1: |[4.9.2 Regression] cc1: |internal compiler error: in |internal compiler error: in |init_reg_sets, at |init_reg_sets, at |reginfo.c:178 |reginfo.c:178 Ever confirmed|0 |1 Build|powerpc-unknown-darwin |powerpc-apple-darwin9 --- Comment #6 from Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> --- (In reply to Lawrence Velázquez from comment #5) > Some MacPorts users are now reporting this. Can you provide a backtrace of the error? In the build directory, run the executable "gcc/cc1" on a test source file (like the empty main program that libgcc configure tries to compile), under the debugger: "lldb -- ./gcc/cc1 test.c" The debugger starts, then you type "r" (without quotes) and enter. It will stop at the point of failure, then you type "bt" and enter again. Paste here the result of that last command. This will help understand where things are going wrong. >From gcc-bugs-return-468088-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 22 17:30:18 2014 Return-Path: <gcc-bugs-return-468088-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 29994 invoked by alias); 22 Nov 2014 17:30:18 -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 29962 invoked by uid 48); 22 Nov 2014 17:30:14 -0000 From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/64028] New: [5 Regression] r211599 caused many vectorizer test failures with -fPIC Date: Sat, 22 Nov 2014 17:30:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 5.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: hjl.tools at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc Message-ID: <bug-64028-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: 2014-11/txt/msg02560.txt.bz2 Content-length: 775 https://gcc.gnu.org/bugzilla/show_bug.cgi?idd028 Bug ID: 64028 Summary: [5 Regression] r211599 caused many vectorizer test failures with -fPIC Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: hjl.tools at gmail dot com CC: hubicka at ucw dot cz On Linux/ia32, r211599 caused many vectorizer test failures with -fPIC, like: FAIL: gcc.dg/vect/vect-7.c scan-tree-dump-times vect "Vectorizing an unaligned a ccess" 0 FAIL: gcc.dg/vect/vect-7.c -flto -ffat-lto-objects scan-tree-dump-times vect "V ectorizing an unaligned access" 0
next prev parent reply other threads:[~2014-11-22 16:54 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-10-31 18:38 [Bug bootstrap/63703] New: " dougmencken at gmail dot com 2014-10-31 18:39 ` [Bug bootstrap/63703] " dougmencken at gmail dot com 2014-10-31 18:47 ` dougmencken at gmail dot com 2014-10-31 19:20 ` dougmencken at gmail dot com 2014-11-03 9:17 ` [Bug bootstrap/63703] [4.9 " rguenth at gcc dot gnu.org 2014-11-03 9:17 ` rguenth at gcc dot gnu.org 2014-11-21 19:32 ` larryv at macports dot org 2014-11-22 16:54 ` fxcoudert at gcc dot gnu.org [this message] 2014-11-23 16:31 ` [Bug bootstrap/63703] [4.9.2 " gcc@Denis-Excoffier.org 2014-11-23 17:36 ` fxcoudert at gcc dot gnu.org 2014-11-23 17:43 ` [Bug bootstrap/63703] [4.9.2/5 Regression] Bootstrap broken on powerpc-apple-darwin, cc1: internal compiler error: in init_reg_sets fxcoudert at gcc dot gnu.org 2014-11-23 17:59 ` iains at gcc dot gnu.org 2014-11-23 18:07 ` fxcoudert at gcc dot gnu.org 2014-11-24 16:31 ` rohitarulraj at gmail dot com 2014-11-24 16:48 ` iains at gcc dot gnu.org 2014-11-24 19:07 ` rohitarulraj at gmail dot com 2014-11-25 6:23 ` misty at brew dot sh 2014-11-25 19:01 ` fxcoudert at gcc dot gnu.org 2014-11-25 21:42 ` fxcoudert at gcc dot gnu.org 2014-11-25 21:55 ` fxcoudert at gcc dot gnu.org 2014-11-26 3:22 ` larryv at macports dot org 2014-11-26 8:11 ` iains at gcc dot gnu.org 2014-11-27 5:47 ` gcc@Denis-Excoffier.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-63703-4-uY6sqOCLOS@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).