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/42509] [4.5 Regression] bootstrap failure in stage3 (integer overflow in preprocessor expression) Date: Thu, 01 Apr 2010 17:11:00 -0000 [thread overview] Message-ID: <20100401171120.18938.qmail@sourceware.org> (raw) In-Reply-To: <bug-42509-11764@http.gcc.gnu.org/bugzilla/> ------- Comment #13 from ramana at gcc dot gnu dot org 2010-04-01 17:11 ------- (In reply to comment #12) > I see this on arm-eabi cross with gcc version 4.5.0 20100401 (experimental) > [trunk revision 157899] (GCC) > > With the following command line options - > > ./xgcc -B`pwd` -S -O2 -mthumb -mcpu=cortex-a9 -mfpu=vfpv3-d16 ~/expr.i -da -g Correction - this should read ./xgcc -B`pwd` -S -O2 -mthumb -mcpu=cortex-a9 -mfpu=vfpv3-d16 ~/expr.i -da -g -mfloat-abi=softfp > > In 203r.sched2 I see the following insn sequence which appears to be wrong to > my naked eye. > > > (insn 5045 1929 5046 167 /home/ramrad01/trunk/libcpp/expr.c:1281 (set (reg:SI 1 > r1) > (plus:SI (reg/f:SI 13 sp) > (const_int 272 [0x110]))) 4 {*arm_addsi3} (nil)) > > (insn:TI 5046 5045 6004 167 /home/ramrad01/trunk/libcpp/expr.c:1281 (set > (reg:DI 0 r0) > (mem/c:DI (reg:SI 1 r1) [87 %sfp S8 A64])) 587 {*thumb2_movdi_vfp} > (nil)) > > (insn 6004 5046 5042 167 /home/ramrad01/trunk/libcpp/expr.c:1281 (parallel [ > (set (reg:SI 3 r3 [+4 ]) > (const_int 0 [0x0])) > (clobber (reg:CC 24 cc)) > ]) 704 {*thumb2_movsi_shortim} (expr_list:REG_UNUSED (reg:CC 24 cc) > (nil))) > > (insn:TI 5042 6004 6002 167 /home/ramrad01/trunk/libcpp/expr.c:1281 (set > (mem/c:SI (plus:SI (reg/f:SI 13 sp) > (const_int 272 [0x110])) [87 %sfp+-544 S4 A64]) > (reg:SI 14 lr)) 585 {*thumb2_movsi_vfp} (expr_list:REG_DEAD (reg:SI 14 > lr) > (nil))) > > (insn:TI 6002 5042 6003 167 /home/ramrad01/trunk/libcpp/expr.c:1281 (parallel [ > (set (reg:SI 3 r3 [+4 ]) > (and:SI (reg:SI 3 r3 [+4 ]) > (reg:SI 1 r1 [+4 ]))) > (clobber (reg:CC 24 cc)) > ]) 700 {*thumb2_alusi3_short} (expr_list:REG_DEAD (reg:SI 1 r1 [+4 ]) > (expr_list:REG_UNUSED (reg:CC 24 cc) > (nil)))) > (In reply to comment #12) > I see this on arm-eabi cross with gcc version 4.5.0 20100401 (experimental) > [trunk revision 157899] (GCC) > > With the following command line options - > > ./xgcc -B`pwd` -S -O2 -mthumb -mcpu=cortex-a9 -mfpu=vfpv3-d16 ~/expr.i -da -g > > > In 203r.sched2 I see the following insn sequence which appears to be wrong to > my naked eye. > > > (insn 5045 1929 5046 167 /home/ramrad01/trunk/libcpp/expr.c:1281 (set (reg:SI 1 > r1) > (plus:SI (reg/f:SI 13 sp) > (const_int 272 [0x110]))) 4 {*arm_addsi3} (nil)) > > (insn:TI 5046 5045 6004 167 /home/ramrad01/trunk/libcpp/expr.c:1281 (set > (reg:DI 0 r0) > (mem/c:DI (reg:SI 1 r1) [87 %sfp S8 A64])) 587 {*thumb2_movdi_vfp} > (nil)) > > (insn 6004 5046 5042 167 /home/ramrad01/trunk/libcpp/expr.c:1281 (parallel [ > (set (reg:SI 3 r3 [+4 ]) > (const_int 0 [0x0])) > (clobber (reg:CC 24 cc)) > ]) 704 {*thumb2_movsi_shortim} (expr_list:REG_UNUSED (reg:CC 24 cc) > (nil))) > > (insn:TI 5042 6004 6002 167 /home/ramrad01/trunk/libcpp/expr.c:1281 (set > (mem/c:SI (plus:SI (reg/f:SI 13 sp) > (const_int 272 [0x110])) [87 %sfp+-544 S4 A64]) > (reg:SI 14 lr)) 585 {*thumb2_movsi_vfp} (expr_list:REG_DEAD (reg:SI 14 > lr) > (nil))) > > (insn:TI 6002 5042 6003 167 /home/ramrad01/trunk/libcpp/expr.c:1281 (parallel [ > (set (reg:SI 3 r3 [+4 ]) > (and:SI (reg:SI 3 r3 [+4 ]) > (reg:SI 1 r1 [+4 ]))) > (clobber (reg:CC 24 cc)) > ]) 700 {*thumb2_alusi3_short} (expr_list:REG_DEAD (reg:SI 1 r1 [+4 ]) > (expr_list:REG_UNUSED (reg:CC 24 cc) > (nil)))) > -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42509
next prev parent reply other threads:[~2010-04-01 17:11 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-12-26 12:03 [Bug target/42509] New: " doko at ubuntu dot com 2009-12-29 10:09 ` [Bug target/42509] " ramana at gcc dot gnu dot org 2009-12-30 23:55 ` ramana at gcc dot gnu dot org 2009-12-31 15:21 ` [Bug target/42509] [4.5 Regression] " rguenth at gcc dot gnu dot org 2010-01-06 12:26 ` ramana at gcc dot gnu dot org 2010-01-07 13:53 ` debian-gcc at lists dot debian dot org 2010-03-15 13:23 ` rguenth at gcc dot gnu dot org 2010-03-15 17:36 ` laurent at guerby dot net 2010-03-16 8:57 ` ramana at gcc dot gnu dot org 2010-03-16 13:56 ` rguenth at gcc dot gnu dot org 2010-04-01 15:03 ` rearnsha at gcc dot gnu dot org 2010-04-01 15:11 ` rearnsha at gcc dot gnu dot org 2010-04-01 15:32 ` rearnsha at gcc dot gnu dot org 2010-04-01 15:55 ` ramana at gcc dot gnu dot org 2010-04-01 17:11 ` ramana at gcc dot gnu dot org [this message] 2010-04-01 19:31 ` rearnsha at gcc dot gnu dot org 2010-04-01 22:04 ` rearnsha at gcc dot gnu dot org 2010-04-01 22:44 ` rearnsha at gcc dot gnu dot org 2010-04-01 23:34 ` [Bug middle-end/42509] " rearnsha at gcc dot gnu dot org 2010-04-02 0:02 ` ramana at gcc dot gnu dot org 2010-04-02 8:08 ` ramana at gcc dot gnu dot org 2010-04-02 12:09 ` rguenth at gcc dot gnu dot org 2010-04-02 12:15 ` rguenth at gcc dot gnu dot org 2010-04-02 12:33 ` rguenth at gcc dot gnu dot org 2010-04-02 13:54 ` rguenth at gcc dot gnu dot org 2010-04-02 15:20 ` rguenth at gcc dot gnu dot org 2010-04-02 16:15 ` rguenth at gcc dot gnu dot org 2010-04-03 17:15 ` rguenth at gcc dot gnu dot org 2010-04-03 17:15 ` rguenth at gcc dot gnu dot org 2010-04-12 19:56 ` [Bug middle-end/42509] [4.4 " steven at gcc dot gnu dot org 2010-04-12 19:58 ` [Bug middle-end/42509] [4.4 Regression] nonoverlapping_memrefs_p misinterprets NULL MEM_OFFSET as const0_rtx steven at gcc dot gnu dot org 2010-04-30 8:58 ` jakub at gcc dot gnu dot org 2010-07-28 18:00 ` uweigand at gcc dot gnu dot org 2010-07-28 18:01 ` uweigand 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=20100401171120.18938.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: linkBe 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).