public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cbaylis at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/38674] When storing in a register the address of a value contained in the same register, gcc 4.3.2 on ARM clobbers the register before saving its content on the stack.
Date: Thu, 19 Feb 2015 11:34:00 -0000	[thread overview]
Message-ID: <bug-38674-4-eSykqgcEHi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-38674-4@http.gcc.gnu.org/bugzilla/>

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

cbaylis at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |cbaylis at gcc dot gnu.org
         Resolution|---                         |DUPLICATE

--- Comment #3 from cbaylis at gcc dot gnu.org ---
This appears to have been fixed by r161920

2010-07-07  Bernd Schmidt  <bernds@codesourcery.com>

        PR rtl-optimization/44404
        * auto-inc-dec.c (find_inc): Avoid calling count_occurrences if
        possible, use reg_overlap_mentioned_p instead.

*** This bug has been marked as a duplicate of bug 44404 ***


       reply	other threads:[~2015-02-19 11:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-38674-4@http.gcc.gnu.org/bugzilla/>
2015-02-19 11:34 ` cbaylis at gcc dot gnu.org [this message]
2008-12-30 16:14 [Bug regression/38674] New: optimization bug gilles dot chanteperdrix at xenomai dot org
2009-01-05 15:21 ` [Bug middle-end/38674] When storing in a register the address of a value contained in the same register, gcc 4.3.2 on ARM clobbers the register before saving its content on the stack gilles dot chanteperdrix at xenomai dot org
2009-03-16 23:38 ` rearnsha at gcc dot gnu dot org
2009-03-16 23:39 ` rearnsha at gcc dot gnu dot 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-38674-4-eSykqgcEHi@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).