public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paul dot richard dot thomas at cea dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/24406] EQUIVALENCE broken in 32-bit code with optimization -O2
Date: Fri, 03 Mar 2006 10:08:00 -0000 [thread overview]
Message-ID: <20060303100825.12231.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24406-10567@http.gcc.gnu.org/bugzilla/>
------- Comment #11 from paul dot richard dot thomas at cea dot fr 2006-03-03 10:08 -------
> Even though the final tree dump looks correct this is a still a front-end issue
> as the front-end communicates the aliasing sets to the rtl optimizers.
> I am going to take it too.
I have either missed something, the PR has fixed itself or it is not a
front-end problem. See below.
Paul
THOMASP@PC-THOMAS-P /cygdrive/d/svn/prs
$ /irun/bin/gfortran --version
GNU Fortran 95 (GCC) 4.2.0 20060301 (experimental)
Copyright (C) 2006 Free Software Foundation, Inc.
THOMASP@PC-THOMAS-P /cygdrive/d/svn/prs
$ uname -a
CYGWIN_NT-5.0 PC-THOMAS-P 1.5.7(0.109/3/2) 2004-01-30 19:32 i686 unknown
unknown
Cygwin
THOMASP@PC-THOMAS-P /cygdrive/d/svn/prs
$ /irun/bin/gfortran -m32 -O3 -Wall -std=f95 -pedantic -fdump-tree-gimple pr244
06.f
THOMASP@PC-THOMAS-P /cygdrive/d/svn/prs
$ ./a
0.99 < rteps < 1.1 : rteps OK
rteps = 1.00000000000000
THOMASP@PC-THOMAS-P /cygdrive/d/svn/prs
$ cat *pr24406*le
MAIN__ ()
{
real8 D.906;
logical4 D.907;
logical4 D.908;
logical4 D.909;
logical4 D.910;
union
{
int4 irt[2];
real8 rteps;
} equiv.0;
int4 irt[2] [value-expr: equiv.0.irt];
real8 rteps [value-expr: equiv.0.rteps];
_gfortran_set_std (2, 11, 1);
equiv.0.irt[0] = 0;
equiv.0.irt[1] = 1072693248;
D.906 = equiv.0.rteps;
D.907 = D.906 > 9.89999999999999991118215802998747676610946655273e-1;
D.908 = !D.907;
if (D.908)
..........snip.............
--
paul dot richard dot thomas at cea dot fr changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |paul dot richard dot thomas
| |at cea dot fr
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24406
next prev parent reply other threads:[~2006-03-03 10:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-17 11:10 [Bug fortran/24406] New: " mick at nag dot co dot uk
2005-10-17 11:29 ` [Bug fortran/24406] " pinskia at gcc dot gnu dot org
2005-10-17 11:30 ` pinskia at gcc dot gnu dot org
2005-10-17 18:01 ` kargl at gcc dot gnu dot org
2005-10-17 18:01 ` kargl at gcc dot gnu dot org
2005-10-23 22:52 ` pinskia at gcc dot gnu dot org
2005-11-01 20:20 ` tobi at gcc dot gnu dot org
2006-02-06 20:33 ` tkoenig at gcc dot gnu dot org
2006-02-06 20:56 ` [Bug rtl-optimization/24406] " tobi at gcc dot gnu dot org
2006-02-06 20:57 ` sgk at troutmask dot apl dot washington dot edu
2006-02-06 21:01 ` [Bug fortran/24406] " pinskia at gcc dot gnu dot org
2006-03-03 10:08 ` paul dot richard dot thomas at cea dot fr [this message]
2006-03-06 21:03 ` pinskia at gcc dot gnu dot org
2006-03-07 7:28 ` paul dot richard dot thomas at cea dot fr
2006-03-23 1:06 ` pinskia at gcc dot gnu dot org
2006-03-23 8:06 ` paul dot richard dot thomas at cea dot fr
2006-03-23 14:54 ` Andrew Pinski
2006-03-23 14:54 ` pinskia at physics dot uc dot edu
2006-04-23 6:07 ` pault at gcc dot gnu dot org
2006-04-24 10:13 ` mick at nag dot co dot uk
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=20060303100825.12231.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: 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).