public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aoliva at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/67891] [6 Regression] FAIL: gcc.dg/pr43300.c (internal compiler error) on alpha-linux-gnu
Date: Fri, 09 Oct 2015 06:18:00 -0000	[thread overview]
Message-ID: <bug-67891-4-DiAH0KSvWb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67891-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67891

--- Comment #2 from Alexandre Oliva <aoliva at gcc dot gnu.org> ---
Created attachment 36469
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36469&action=edit
Patch that works around the problem

Ugh.  assign_parms's use of emit_block_move (as for parameter a in this
testcase) marks decls as addressable that weren't before, so they no longer
pass is_gimple_reg in spite of having SSA defs.  This is turn causes
set_parm_rtl to pass the parm down to set_rtl, instead of the default def, so
the RTL isn't associated with the partition holding the default def.  Oops.

Fortunately, ssa_default_def doesn't seem to mind being called for addressable
decls, so we can just skip the is_gimple_reg test.  I'm testing further to see
that this is indeed the case.


  parent reply	other threads:[~2015-10-09  6:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-08  7:58 [Bug middle-end/67891] New: " ubizjak at gmail dot com
2015-10-08  9:08 ` [Bug middle-end/67891] " rguenth at gcc dot gnu.org
2015-10-09  5:37 ` aoliva at gcc dot gnu.org
2015-10-09  6:18 ` aoliva at gcc dot gnu.org [this message]
2015-10-09  8:12 ` rguenth at gcc dot gnu.org
2015-10-09 12:19 ` aoliva at gcc dot gnu.org
2015-10-09 12:22 ` aoliva 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-67891-4-DiAH0KSvWb@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: link
Be 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).