public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/47714] [4.6 Regression] verify_ssa fails with error: invalid argument to gimple call
Date: Wed, 09 Mar 2011 08:43:00 -0000	[thread overview]
Message-ID: <bug-47714-4-yC2BF0WyBy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47714-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47714

--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-03-09 08:43:32 UTC ---
BTW, if you adjust the testcase (at least not to use explicit DImode type), I'd
say this patch is obvious, thunks never take addresses of its parameters and
whether the original method takes those addresses is irrelevant to thunks.
You could certainly handle TREE_ADDRESSABLE in assemble_thunk by copying siuch
arguments into a temporary, but that would be good just to shut up
verification.


  parent reply	other threads:[~2011-03-09  8:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-13  0:54 [Bug tree-optimization/47714] New: " jamborm at gcc dot gnu.org
2011-02-13  0:56 ` [Bug tree-optimization/47714] " jamborm at gcc dot gnu.org
2011-02-13  1:18 ` jamborm at gcc dot gnu.org
2011-02-13 10:12 ` rguenth at gcc dot gnu.org
2011-03-02 15:16 ` jamborm at gcc dot gnu.org
2011-03-08 16:57 ` [Bug tree-optimization/47714] [4.6 Regression] " rguenth at gcc dot gnu.org
2011-03-08 17:07 ` rguenth at gcc dot gnu.org
2011-03-08 20:42 ` jakub at gcc dot gnu.org
2011-03-08 20:46 ` jamborm at gcc dot gnu.org
2011-03-09  8:43 ` jakub at gcc dot gnu.org [this message]
2011-03-09 12:02 ` jamborm at gcc dot gnu.org
2011-03-09 17:00 ` jamborm at gcc dot gnu.org
2011-03-09 17:02 ` jamborm 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-47714-4-yC2BF0WyBy@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).