public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "venkataramanan.kumar at amd dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/55845] 454.calculix miscompares with -march=btver2 -O3 -ffastmath -fschedule-insns -mvzeroupper for test data run
Date: Fri, 04 Jan 2013 09:12:00 -0000 [thread overview]
Message-ID: <bug-55845-4-6AfwghQWBY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55845-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55845
--- Comment #5 from Venkataramanan <venkataramanan.kumar at amd dot com> 2013-01-04 09:12:09 UTC ---
Hi Uros.
Thank you for conforming.
I suspected this is a problem with jump optimization. Uros what flag we need
to pass to bypass the .jump2 pass?
Regards,
Venkat.
-----Original Message-----
From: ubizjak at gmail dot com [mailto:gcc-bugzilla@gcc.gnu.org]
Sent: Friday, January 04, 2013 1:43 PM
To: Kumar, Venkataramanan
Subject: [Bug rtl-optimization/55845] 454.calculix miscompares with
-march=btver2 -O3 -ffastmath -fschedule-insns -mvzeroupper for test data run
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55845
Uros Bizjak <ubizjak at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2013-01-04
Ever Confirmed|0 |1
--- Comment #4 from Uros Bizjak <ubizjak at gmail dot com> 2013-01-04 08:13:03
UTC --- Please note how unspec_volatile vzeroupper (insn 225) moves above
conditional jump comparison, passing many instructions:
_.c.218r.csa:
...
110: {r8:SI=r8:SI+r11:SI;clobber flags:CC;}
REG_UNUSED flags:CC
111: flags:CCZ=cmp(bx:SI,r11:SI)
REG_DEAD r11:SI
REG_DEAD bx:SI
105: xmm2:V4DF=vec_select(vec_concat(xmm1:V4DF,xmm1:V4DF),parallel)
106: xmm1:V4DF=xmm1:V4DF+xmm2:V4DF
REG_DEAD xmm2:V4DF
234: xmm1:V2DF=xmm1:V2DF
235: xmm1:DF=xmm1:DF
109: xmm0:DF=xmm0:DF+xmm1:DF
REG_DEAD xmm1:DF
112: pc={(flags:CCZ==0)?L230:pc}
REG_DEAD flags:CCZ
REG_BR_PROB 0xd06
226: NOTE_INSN_BASIC_BLOCK 22
225: unspec/v[0] 43
113: L113:
114: NOTE_INSN_BASIC_BLOCK 23
...
_.c.219r.jump2:
...
110: {r8:SI=r8:SI+r11:SI;clobber flags:CC;}
REG_UNUSED flags:CC
225: unspec/v[0] 43
111: flags:CCZ=cmp(bx:SI,r11:SI)
REG_DEAD r11:SI
REG_DEAD bx:SI
105: xmm2:V4DF=vec_select(vec_concat(xmm1:V4DF,xmm1:V4DF),parallel)
106: xmm1:V4DF=xmm1:V4DF+xmm2:V4DF
REG_DEAD xmm2:V4DF
109: xmm0:DF=xmm0:DF+xmm1:DF
REG_DEAD xmm1:DF
112: pc={(flags:CCZ==0)?L231:pc}
REG_DEAD flags:CCZ
REG_BR_PROB 0xd06
113: L113:
114: NOTE_INSN_BASIC_BLOCK 23
...
Confirmed as rtl-optimization infrastructure problem.
--
Configure bugmail: http://gcc.gnu.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: ------- You reported the bug.
next prev parent reply other threads:[~2013-01-04 9:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-02 9:28 [Bug rtl-optimization/55845] New: " venkataramanan.kumar at amd dot com
2013-01-02 10:10 ` [Bug rtl-optimization/55845] " ubizjak at gmail dot com
2013-01-02 10:15 ` ubizjak at gmail dot com
2013-01-04 6:41 ` vbyakovl23 at gmail dot com
2013-01-04 8:13 ` ubizjak at gmail dot com
2013-01-04 9:12 ` venkataramanan.kumar at amd dot com [this message]
2013-01-04 9:20 ` ubizjak at gmail dot com
2013-01-04 9:25 ` venkataramanan.kumar at amd dot com
2013-01-04 9:35 ` [Bug rtl-optimization/55845] [4.8 Regression] " ubizjak at gmail dot com
2013-01-06 13:24 ` ubizjak at gmail dot com
2013-01-06 15:51 ` ubizjak at gmail dot com
2013-01-07 15:46 ` rguenth at gcc dot gnu.org
2013-01-08 18:01 ` jakub at gcc dot gnu.org
2013-01-08 18:04 ` jakub at gcc dot gnu.org
2013-01-15 14:05 ` venkataramanan.kumar at amd dot com
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-55845-4-6AfwghQWBY@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).