public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "christophe.lyon at st dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/59289] New: [ARM] regression on unsigned-extend-2.c
Date: Mon, 25 Nov 2013 16:07:00 -0000	[thread overview]
Message-ID: <bug-59289-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 59289
           Summary: [ARM] regression on unsigned-extend-2.c
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: christophe.lyon at st dot com

Since commit 203160 (New rtx costs infrastructure for ARM), I have noticed that
gcc.target/arm/unsigned-extend-2.c scan-assembler ands
gcc.target/arm/unsigned-extend-2.c scan-assembler-not cmp
now FAIL (used to PASS).

I have configured GCC as:
target: arm-none-linux-gnueabihf
mode: thumb
cpu: cortex-a15
fpu: neon-vfpv4

With r203159:
    movs    r3, #8
.L3:
    lsrs    r0, r0, #1
    subs    r3, r3, #1
    ands    r3, r3, #255
    bne    .L3
    bx    lr

with r203160:
    movs    r3, #0
.L3:
    lsrs    r0, r0, #1
    adds    r3, r3, #1
    cmp    r3, #8
    bne    .L3
    bx    lr

It seems that code gen has slightly evolved in trunk since r203160, but the
test still fails.

The code sequence does not seem really worse than the original one, but the
testcase should at least be updated.


             reply	other threads:[~2013-11-25 16:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-25 16:07 christophe.lyon at st dot com [this message]
2013-11-26  9:10 ` [Bug target/59289] [4.9 Regression][ARM] " rguenth at gcc dot gnu.org
2013-11-27  9:57 ` [Bug target/59289] [ARM] " ktkachov at gcc dot gnu.org
2013-11-29 15:19 ` ktkachov at gcc dot gnu.org
2013-11-29 15:20 ` ktkachov 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-59289-4@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).