public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rearnsha at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/39429] compiler create bad asm codes.
Date: Mon, 16 Mar 2009 22:53:00 -0000 [thread overview]
Message-ID: <20090316225312.27737.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39429-17427@http.gcc.gnu.org/bugzilla/>
------- Comment #2 from rearnsha at gcc dot gnu dot org 2009-03-16 22:53 -------
Confirmed. This is a bug in the arith_adjacent_mem pattern that only triggers
when the offset to the memory from the base pointer exceeds the range of a
simple add instruction (ie more than 1024 bytes). In that case we fall back to
emitting two ldr instructions, but fail to consider the case when the first
load overwrites the base address.
--
rearnsha at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rearnsha at gcc dot gnu dot
| |org, ramana dot r at gmail
| |dot com
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Last reconfirmed|0000-00-00 00:00:00 |2009-03-16 22:53:12
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39429
next prev parent reply other threads:[~2009-03-16 22:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 7:25 [Bug c++/39429] New: " ryos at sinby dot com
2009-03-12 1:19 ` [Bug c++/39429] " ryos at sinby dot com
2009-03-16 22:53 ` rearnsha at gcc dot gnu dot org [this message]
2009-03-16 23:02 ` [Bug target/39429] " rearnsha at gcc dot gnu dot org
2009-07-11 20:20 ` mikpe at it dot uu dot se
2009-07-12 11:30 ` mikpe at it dot uu dot se
2009-07-12 20:51 ` ramana at gcc dot gnu dot org
2009-07-12 21:21 ` mikpe at it dot uu dot se
2009-07-12 23:58 ` mikpe at it dot uu dot se
2009-07-13 13:06 ` mikpe at it dot uu dot se
2009-07-13 13:07 ` mikpe at it dot uu dot se
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=20090316225312.27737.qmail@sourceware.org \
--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).