public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/49719] [4.7 Regression] test gcc.target/arm/sibcall-1.c fails for ARM
Date: Wed, 13 Jul 2011 09:46:00 -0000	[thread overview]
Message-ID: <bug-49719-4-XLzd9QbDoz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49719-4@http.gcc.gnu.org/bugzilla/>

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

Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2011.07.13 09:45:43
                 CC|                            |ebotcazou at gcc dot
                   |                            |gnu.org
     Ever Confirmed|0                           |1

--- Comment #1 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2011-07-13 09:45:43 UTC ---
The sibcall still works on x86 but is indeed disabled on ARM because of the
lack of [reg+disp] addressing mode.  While on x86 you have:

(insn 15 14 16 3 (set (reg:SI 67)
        (mem/s/c:SI (plus:SI (reg/f:SI 53 virtual-incoming-args)
                (const_int 32 [0x20])) [3 a+8 S4 A32])) sibcall-1.c:22 -1
     (nil))

(insn 16 15 17 3 (set (mem:SI (plus:SI (reg/f:SI 53 virtual-incoming-args)
                (const_int 16 [0x10])) [0 S4 A32])
        (reg:SI 67)) sibcall-1.c:22 -1
     (nil))

on ARM you have instead:

(insn 21 10 22 3 (set (reg:SI 143)
        (reg/f:SI 131 virtual-outgoing-args)) sibcall-1.c:22 -1
     (nil))

(insn 22 21 23 3 (set (reg:SI 144)
        (plus:SI (reg/f:SI 128 virtual-incoming-args)
            (const_int 16 [0x10]))) sibcall-1.c:22 -1
     (nil))

(insn 23 22 24 3 (parallel [
            (set (reg:SI 0 r0)
                (mem/s/c:SI (reg:SI 144) [3 a+8 S4 A32]))
            (set (reg:SI 1 r1)
                (mem/s/c:SI (plus:SI (reg:SI 144)
                        (const_int 4 [0x4])) [3 a+12 S4 A32]))
        ]) sibcall-1.c:22 -1
     (nil))

(insn 24 23 25 3 (parallel [
            (set (mem:SI (reg:SI 143) [0 S4 A32])
                (reg:SI 0 r0))
            (set (mem:SI (plus:SI (reg:SI 143)
                        (const_int 4 [0x4])) [0 S4 A32])
                (reg:SI 1 r1))
        ]) sibcall-1.c:22 -1
     (nil))

so mem_overlaps_already_clobbered_arg_p doesn't see the displacement in the
effective address of the load.  Quite annoying.


  parent reply	other threads:[~2011-07-13  9:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-12 15:05 [Bug middle-end/49719] New: " janis at gcc dot gnu.org
2011-07-12 20:39 ` [Bug middle-end/49719] [4.7 Regression] " rguenth at gcc dot gnu.org
2011-07-13  9:46 ` ebotcazou at gcc dot gnu.org [this message]
2011-10-10 12:19 ` rguenth at gcc dot gnu.org
2011-11-28 15:33 ` jakub at gcc dot gnu.org
2011-11-29 10:18 ` jakub at gcc dot gnu.org
2011-12-05  8:41 ` jakub 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-49719-4-XLzd9QbDoz@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).