public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ramana at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/43698] [4.5/4.6 Regression] Wrong use of ARMv6 REV instruction for endian bytewapping with -Os or -O2 optimizations
Date: Fri, 30 Jul 2010 22:36:00 -0000	[thread overview]
Message-ID: <20100730223606.7473.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43698-14457@http.gcc.gnu.org/bugzilla/>



------- Comment #17 from ramana at gcc dot gnu dot org  2010-07-30 22:36 -------
Subject: Bug 43698

Author: ramana
Date: Fri Jul 30 22:35:40 2010
New Revision: 162725

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=162725
Log:
Backport fix for PR target/43698.

2010-07-30  Ramana Radhakrishnan  <ramana.radhakrishnan@arm.com>

        Backport from mainline.
        2010-07-22  Ramana Radhakrishnan  <ramana.radhakrishnan@arm.com>

        PR target/43698
        * config/arm/arm.md: Split arm_rev into *arm_rev and *thumb1_rev.
        Set *arm_rev to be predicable.

2010-07-30  Ramana Radhakrishnan  <ramana.radhakrishnan@arm.com>

        Backport from mainline
        2010-07-22  Ramana Radhakrishnan  <ramana.radhakrishnan@arm.com>

        PR target/43698
        * gcc.target/arm/pr43698.c: New test.


Added:
    branches/gcc-4_5-branch/gcc/testsuite/gcc.target/arm/pr43698.c
      - copied unchanged from r162404,
trunk/gcc/testsuite/gcc.target/arm/pr43698.c
Modified:
    branches/gcc-4_5-branch/   (props changed)
    branches/gcc-4_5-branch/gcc/ChangeLog
    branches/gcc-4_5-branch/gcc/config/arm/arm.md
    branches/gcc-4_5-branch/gcc/testsuite/ChangeLog

Propchange: branches/gcc-4_5-branch/
            ('svn:mergeinfo' added)


-- 


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


  parent reply	other threads:[~2010-07-30 22:36 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-09  0:05 [Bug c/43698] New: Invalid code when building gentoo pax-utils-0.1.19 with -Os optimizations siarhei dot siamashka at gmail dot com
2010-04-09  5:49 ` [Bug target/43698] " mikpe at it dot uu dot se
2010-04-09  6:57 ` mikpe at it dot uu dot se
2010-04-09  7:02 ` ramana at gcc dot gnu dot org
2010-04-09  7:38 ` ramana at gcc dot gnu dot org
2010-04-09  7:49 ` ramana at gcc dot gnu dot org
2010-04-09  8:05 ` siarhei dot siamashka at gmail dot com
2010-04-09  8:42 ` [Bug target/43698] [4.5/4.6 Regression] " rguenth at gcc dot gnu dot org
2010-04-12  8:38 ` ramana at gcc dot gnu dot org
2010-04-12  9:34 ` siarhei dot siamashka at gmail dot com
2010-04-12  9:51   ` Ramana Radhakrishnan
2010-04-12  9:51 ` ramana dot radhakrishnan at arm dot com
2010-05-17 18:48 ` siarhei dot siamashka at gmail dot com
2010-05-19 12:25 ` rguenth at gcc dot gnu dot org
2010-07-03 16:06 ` armin76 at gentoo dot org
2010-07-19 13:54 ` [Bug target/43698] [4.5/4.6 Regression] Wrong use of ARMv6 REV instruction for endian bytewapping with -Os or -O2 optimizations siarhei dot siamashka at gmail dot com
2010-07-22  8:31 ` ramana at gcc dot gnu dot org
2010-07-22 20:54 ` siarhei dot siamashka at gmail dot com
2010-07-23 12:22 ` ramana at gcc dot gnu dot org
2010-07-23 12:28 ` rguenther at suse dot de
2010-07-30 22:36 ` ramana at gcc dot gnu dot org [this message]
2010-07-30 22:39 ` ramana 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=20100730223606.7473.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).