public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ramana at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/49452] comp-goto-2.c regresses in testing
Date: Sat, 18 Jun 2011 08:38:00 -0000	[thread overview]
Message-ID: <bug-49452-4-EANfIKs3cf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49452-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Ramana Radhakrishnan <ramana at gcc dot gnu.org> 2011-06-18 08:37:06 UTC ---
(In reply to comment #3)
> > I haven't looked at in great detail yet to analyse what causes this problem but
> > it appears to have appeared in the last week or so.
> 
> Maybe r175063 (significant dse.c change).

It does appear to be that revision triggering this change. 
The problem essentially here is that the backend generates 


(insn/f 36 35 37 2 (set (reg/f:SI 11 fp)
        (plus:SI (reg/f:SI 13 sp)
            (const_int 96 [0x60])))
/home/ramrad01/sources/fsf/trunk/gcc/testsuite/gcc.c-torture/execute/comp-goto-2.c:11
-1
     (nil))

(insn/f 37 36 38 2 (set (reg/f:SI 13 sp)
        (plus:SI (reg/f:SI 13 sp)
            (const_int -28 [0xffffffffffffffe4])))
/home/ramrad01/sources/fsf/trunk/gcc/testsuite/gcc.c-torture/execute/comp-goto-2.c:11
-1
     (nil))

(insn 38 37 39 2 (set (mem:BLK (scratch) [0 A8])
        (unspec:BLK [
                (reg/f:SI 13 sp)
                (reg/f:SI 11 fp)
            ] UNSPEC_PRLG_STK))
/home/ramrad01/sources/fsf/trunk/gcc/testsuite/gcc.c-torture/execute/comp-goto-2.c:11
-1
     (nil))

(note 39 38 5 2 NOTE_INSN_PROLOGUE_END)

(note 5 39 8 2 NOTE_INSN_FUNCTION_BEG)

(note 8 5 9 2 NOTE_INSN_DELETED)

(insn 9 8 2 2 (set (reg:SI 12 ip)
        (plus:SI (reg/f:SI 11 fp)
            (const_int -112 [0xffffffffffffff90])))
/home/ramrad01/sources/fsf/trunk/gcc/testsuite/gcc.c-torture/execute/comp-goto-2.c:23
4 {*arm_addsi3}
     (nil))

(insn 2 9 33 2 (set (mem/c:SI (plus:SI (reg/f:SI 11 fp)
                (const_int -120 [0xffffffffffffff88])) [6 %sfp+-20 S4 A32])
        (reg:SI 0 r0 [ a ]))
/home/ramrad01/sources/fsf/trunk/gcc/testsuite/gcc.c-torture/execute/comp-goto-2.c:11
632 {*arm_movsi_vfp}
     (nil))

(insn 33 2 3 2 (set (reg:SI 3 r3)
        (plus:SI (reg/f:SI 11 fp)
            (const_int -100 [0xffffffffffffff9c])))
/home/ramrad01/sources/fsf/trunk/gcc/testsuite/gcc.c-torture/execute/comp-goto-2.c:11
4 {*arm_addsi3}
     (nil))

(insn 3 33 4 2 (set (mem/s/f/c:SI (plus:SI (reg/f:SI 11 fp)
                (const_int -112 [0xffffffffffffff90])) [5
FRAME.0.__nl_goto_buf+0 S4 A32])
        (reg:SI 3 r3))
/home/ramrad01/sources/fsf/trunk/gcc/testsuite/gcc.c-torture/execute/comp-goto-2.c:11
632 {*arm_movsi_vfp}
     (nil))

(insn 4 3 11 2 (set (mem/s/f/c:SI (plus:SI (reg/f:SI 11 fp)
                (const_int -108 [0xffffffffffffff94])) [5
FRAME.0.__nl_goto_buf+4 S4 A32])
        (reg/f:SI 13 sp))
/home/ramrad01/sources/fsf/trunk/gcc/testsuite/gcc.c-torture/execute/comp-goto-2.c:11
632 {*arm_movsi_vfp}
     (nil))



but the corresponding load into r0 is from a different offset but the alias
sets appear to be correct. 


(insn 24 16 30 3 (set (reg/i:SI 0 r0)
        (mem/c:SI (plus:SI (reg/f:SI 11 fp)
                (const_int -20 [0xffffffffffffffec])) [6 %sfp+-20 S4 A32]))
/home/ramrad01/sources/fsf/trunk/gcc/testsuite/gcc.c-torture/execute/comp-goto-2.c:26
632 {*arm_movsi_vfp}
     (nil))



cheers
Ramana


  parent reply	other threads:[~2011-06-18  8:38 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-17 11:55 [Bug tree-optimization/49452] New: New testsuite failures with arm-linux-gnueabi comp-goto failing with ramana at gcc dot gnu.org
2011-06-17 12:02 ` [Bug tree-optimization/49452] " ramana at gcc dot gnu.org
2011-06-17 16:52 ` [Bug tree-optimization/49452] comp-goto-2.c regresses in testing ebotcazou at gcc dot gnu.org
2011-06-17 16:56 ` ebotcazou at gcc dot gnu.org
2011-06-18  8:38 ` ramana at gcc dot gnu.org [this message]
2011-06-20 14:53 ` ramana at gcc dot gnu.org
2011-06-24 22:01 ` janis at gcc dot gnu.org
2011-06-24 22:20 ` eraman at google dot com
2011-06-24 23:03 ` janis at gcc dot gnu.org
2011-06-24 23:05 ` janis at gcc dot gnu.org
2011-06-24 23:06 ` janis at gcc dot gnu.org
2011-06-24 23:09 ` eraman at google dot com
2011-06-27 18:06 ` janis at gcc dot gnu.org
2011-07-14  8:46 ` [Bug tree-optimization/49452] [4.7 regression] " ebotcazou at gcc dot gnu.org
2011-07-14 17:17 ` eraman at google dot com
2011-07-14 22:11 ` eraman at google dot com
2011-07-15  6:26 ` ebotcazou at gcc dot gnu.org
2011-07-16 21:19 ` ebotcazou at gcc dot gnu.org
2011-07-18 16:33 ` ramana at gcc dot gnu.org
2011-07-18 16:36 ` ramana at gcc dot gnu.org
2011-07-18 17:59 ` ebotcazou at gcc dot gnu.org
2011-09-13  8:45 ` carrot at google dot com
2011-09-14  6:27 ` carrot at google dot com
2011-09-14  7:18 ` ebotcazou at gcc dot gnu.org
2011-09-14 20:55 ` ramana.r at gmail dot com
2011-09-16  7:23 ` carrot at google dot com
2011-09-16 22:05 ` ebotcazou at gcc dot gnu.org
2011-09-20  2:08 ` [Bug rtl-optimization/49452] " carrot at gcc dot gnu.org
2011-10-10 12:22 ` rguenth 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-49452-4-EANfIKs3cf@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).