public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/65240] [5 Regression] ICE (insn does not satisfy its constraints) on powerpc64le-linux-gnu Date: Tue, 03 Mar 2015 20:42:00 -0000 [thread overview] Message-ID: <bug-65240-4-IFrdjdvh5q@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65240-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65240 --- Comment #7 from Martin Sebor <msebor at gcc dot gnu.org> --- I also cannot reproduce the ICE with the original test case but I can confirm it with the test case from comment #6. The test case isn't strictly conforming (as pointed out by a number warnings when -Wall is used). Resolving the problems (declaring fn5, adding the missing return statements, or initializing the local variables a in fn3) makes the ICE disappear. The problem was introduced in r219854: commit 5379d8d457b300219d3d8eda38caaa9916f98078 Author: dje <dje@138bc75d-0d04-0410-961f-82ee72b054a4> Date: Mon Jan 19 18:33:24 2015 +0000 * config/rs6000/default64.h: Include rs6000-cpus.def. (TARGET_DEFAULT) [LITTLE_ENDIAN]: Use ISA 2.7 (POWER8). (TARGET_DEFAULT) [BIG_ENDIAN]: Use POWER4. * config/rs6000/driver-rs6000.c (detect_processor_aix): Add POWER7 and POWER8. * config/rs6000/linux64.h (PROCESSOR_DEFAULT64): Always default to POWER8. * config/rs6000/rs6000.c (rs6000_file_start): Emit .machine pseudo-op to specify assembler dialect. git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@219854 138bc75d-0d04-0410-961f-82ee72b054a4
next prev parent reply other threads:[~2015-03-03 20:42 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-27 17:20 [Bug target/65240] New: " doko at gcc dot gnu.org 2015-03-02 8:45 ` [Bug target/65240] " rguenth at gcc dot gnu.org 2015-03-02 11:36 ` mpolacek at gcc dot gnu.org 2015-03-02 11:40 ` trippels at gcc dot gnu.org 2015-03-02 12:22 ` doko at gcc dot gnu.org 2015-03-02 12:23 ` doko at gcc dot gnu.org 2015-03-02 12:25 ` doko at gcc dot gnu.org 2015-03-02 12:49 ` trippels at gcc dot gnu.org 2015-03-03 20:42 ` msebor at gcc dot gnu.org [this message] 2015-03-03 22:15 ` dje at gcc dot gnu.org 2015-03-03 22:27 ` meissner at gcc dot gnu.org 2015-03-03 22:31 ` msebor at gcc dot gnu.org 2015-03-03 22:49 ` law at redhat dot com 2015-03-04 18:20 ` meissner at gcc dot gnu.org 2015-03-04 21:22 ` meissner at gcc dot gnu.org 2015-03-04 21:24 ` meissner at gcc dot gnu.org 2015-03-16 19:31 ` meissner at gcc dot gnu.org 2015-03-19 23:33 ` meissner at gcc dot gnu.org 2015-03-19 23:37 ` meissner at gcc dot gnu.org 2015-04-03 23:17 ` amodra 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-65240-4-IFrdjdvh5q@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).