public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/66823] New: -ftree-loop-if-convert-stores miscompiles gfortran.dg/elemental_optional_args_3.f90
Date: Thu, 09 Jul 2015 12:09:00 -0000 [thread overview]
Message-ID: <bug-66823-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66823
Bug ID: 66823
Summary: -ftree-loop-if-convert-stores miscompiles
gfortran.dg/elemental_optional_args_3.f90
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Keywords: wrong-code
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: rguenth at gcc dot gnu.org
Target Milestone: ---
Target: i?86-*-*
On x86_64 with -m32/-ftree-loop-if-convert-stores I see
FAIL: gfortran.dg/elemental_optional_args_3.f90 -O3 -fomit-frame-pointer
execution test
FAIL: gfortran.dg/elemental_optional_args_3.f90 -O3 -fomit-frame-pointer
-funroll-loops execution test
FAIL: gfortran.dg/elemental_optional_args_3.f90 -O3 -fomit-frame-pointer
-funroll-all-loops -finline-functions execution test
FAIL: gfortran.dg/elemental_optional_args_3.f90 -O3 -g execution test
if-conversion changes
if (p != 0)
val = *p;
else
val = 1;
to
tem = *p;
val = p != 0 ? tem : 1;
next reply other threads:[~2015-07-09 12:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 12:09 rguenth at gcc dot gnu.org [this message]
2015-07-09 12:12 ` [Bug tree-optimization/66823] " rguenth at gcc dot gnu.org
2015-07-09 12:13 ` rguenth at gcc dot gnu.org
2015-07-09 12:52 ` rguenth at gcc dot gnu.org
2015-07-10 7:53 ` rguenth at gcc dot gnu.org
2015-07-10 12:34 ` 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-66823-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).