public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nickc at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/64010] [msp430-elf] struct function dereference clobbers parameter passed to function
Date: Tue, 02 Dec 2014 16:34:00 -0000	[thread overview]
Message-ID: <bug-64010-4-53esFfgfJX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64010-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Nick Clifton <nickc at redhat dot com> ---
Hi Alex,

  This appears to be a reload bug.  Before reload we have:

(call_insn 12 (call:HI (mem:HI (mem:HI (plus:HI (reg:HI R14)
                                                (const_int 2))))
                       (const_int 0)) 

  After reload this becomes:

(insn 17 (set (reg:HI R14)
              (mem:HI (plus:HI (reg:HI R14)
                               (const_int 2)))))
(call_insn 12 (call:HI (mem:HI (reg:HI R14))
                       (const_int 0)))

  The uploaded patch fixes this but, not being a reload expert, I am not sure
if this is the correct way to solve the problem.  It also seems suspicious that
if this is a generic reload problem, then why has it not been reported and
fixed before now ?


  reply	other threads:[~2014-12-02 16:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-21  3:08 [Bug rtl-optimization/64010] New: " amykyta3 at gmail dot com
2014-12-02 16:34 ` nickc at redhat dot com [this message]
2014-12-02 17:45 ` [Bug rtl-optimization/64010] " uweigand at gcc dot gnu.org
2014-12-02 17:46 ` uweigand at gcc dot gnu.org
2014-12-03  0:20 ` pab at pabigot dot com
2014-12-03  0:31 ` pab at pabigot dot com
2014-12-03  3:25 ` amykyta3 at gmail dot com
2014-12-03 12:50 ` nickc at redhat dot com
2014-12-03 21:59 ` uweigand at gcc dot gnu.org
2014-12-03 22:07 ` uweigand at gcc dot gnu.org
2014-12-17 15:08 ` uweigand at gcc dot gnu.org
2014-12-17 15:09 ` uweigand at gcc dot gnu.org
2014-12-17 15:09 ` uweigand 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-64010-4-53esFfgfJX@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).