public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jgreenhalgh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/61608] New: [4.10 regression] FAIL: gcc.target/arm/epilog-1.c scan-assembler tests
Date: Wed, 25 Jun 2014 12:57:00 -0000	[thread overview]
Message-ID: <bug-61608-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 61608
           Summary: [4.10 regression] FAIL: gcc.target/arm/epilog-1.c
                    scan-assembler tests
           Product: gcc
           Version: 4.10.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: rtl-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: jgreenhalgh at gcc dot gnu.org

Revision 211919 changes the position of the peephole2 pass causing a code-size
regression for ARM targets.

My compiler is configured with:

Target: arm-none-eabi
Configured with: /work/gcc-clean/src/gcc/configure --target=arm-none-eabi
--prefix=/work/gcc-clean/build-arm-none-eabi/install
--with-gmp=/work/gcc-clean/build-arm-none-eabi/host-tools
--with-mpfr=/work/gcc-clean/build-arm-none-eabi/host-tools
--with-mpc=/work/gcc-clean/build-arm-none-eabi/host-tools
--with-pkgversion=unknown --disable-shared --disable-nls --disable-threads
--disable-tls --enable-checking=yes --enable-languages=c,c++,fortran
--with-newlib --with-arch=armv8-a --with-float=hard
--with-fpu=crypto-neon-fp-armv8
Thread model: single
gcc version 4.10.0 20140624

---
Code generation Before:

foo:
    @ args = 0, pretend = 0, frame = 0
    @ frame_needed = 0, uses_anonymous_args = 0
    push    {r4, lr}
    ldr    r4, .L6
    ldr    r4, [r4]
    lsls    r4, r4, #29
    it    mi
    addmi    r2, r2, #1
    bl    bar
    movs    r0, #0
    pop    {r4, pc}
.
---
Code generation After:

foo:
    @ args = 0, pretend = 0, frame = 0
    @ frame_needed = 0, uses_anonymous_args = 0
    push    {r4, lr}
    ldr    r4, .L6
    ldr    r4, [r4]
    tst    r4, #4
    it    ne
    addne    r2, r2, #1
    bl    bar
    movs    r0, #0
    pop    {r4, pc}
---

The tst (immediate) instruction is a 4-byte thumb instruction, while lsls is a
2-byte thumb instruction.


             reply	other threads:[~2014-06-25 12:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-25 12:57 jgreenhalgh at gcc dot gnu.org [this message]
2014-06-25 13:00 ` [Bug rtl-optimization/61608] " jgreenhalgh at gcc dot gnu.org
2014-06-25 13:05 ` ktietz at gcc dot gnu.org
2014-06-25 13:20 ` jgreenhalgh at gcc dot gnu.org
2014-06-25 13:27 ` ktietz at gcc dot gnu.org
2014-06-25 13:52 ` rguenth at gcc dot gnu.org
2014-06-25 13:53 ` rguenth at gcc dot gnu.org
2014-06-30 20:15 ` rth at gcc dot gnu.org
2014-08-06 14:40 ` jgreenhalgh 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-61608-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).