public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "siarhei dot siamashka at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/45094] [arm] wrong instructions for dword move in some cases
Date: Tue, 27 Jul 2010 20:07:00 -0000	[thread overview]
Message-ID: <20100727200711.12618.qmail@sourceware.org> (raw)
In-Reply-To: <bug-45094-19487@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from siarhei dot siamashka at gmail dot com  2010-07-27 20:07 -------
Created an attachment (id=21327)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21327&action=view)
simplified testcase

Confirmed with gcc 4.5.0 here. Also tried but could not reproduce the problem
with gcc 4.4 (it just does not seem to be able to emit ldrd/strd instructions
with pre/post increment).


-- 


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


  parent reply	other threads:[~2010-07-27 20:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-27 11:34 [Bug target/45094] New: " akos dot pasztory at gmail dot com
2010-07-27 12:48 ` [Bug target/45094] " ramana at gcc dot gnu dot org
2010-07-27 20:07 ` siarhei dot siamashka at gmail dot com [this message]
2010-08-01  8:44 ` qiyao at gcc dot gnu dot org
2010-08-01 11:18 ` akos dot pasztory at gmail dot com
2010-08-02  0:39 ` qiyao at gcc dot gnu dot org
2010-08-18 12:34 ` qiyao at gcc dot gnu dot org
2010-08-27 12:14 ` ramana at gcc dot gnu dot org
     [not found] <bug-45094-4@http.gcc.gnu.org/bugzilla/>
2010-12-16 13:22 ` rguenth at gcc dot gnu.org
2010-12-18 15:44 ` siarhei.siamashka at gmail dot com
2010-12-18 15:47 ` siarhei.siamashka at gmail dot com
2010-12-27  8:35 ` qiyao at gcc dot gnu.org
2010-12-28  0:47 ` dirtyepic at gentoo dot org
2010-12-28  1:49 ` qiyao at gcc dot gnu.org
2012-01-12 20:35 ` pinskia 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=20100727200711.12618.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).