--- Comment #3 from jv244 at cam dot ac dot uk 2007-06-29 07:13 ---
I'm wondering if it is still required to turn fortran testcases in the
equivalent C testcase in order to mark this kind of bugs as P1. This does seem
a bit of a waste of time... and just think about the engineers using
--- Comment #1 from ubizjak at gmail dot com 2007-06-28 08:13 ---
Looks like problems in tree ifcvt pass. Before ifcvt, we have:
M.2_16 = (int4) D.1257_15;
if (M.2_16 1) goto L7; else goto L9;
L7:;
if (M.2_16 20) goto L10; else goto L9;
# M.2_64 = PHI M.2_16(6), 1(5);
L9:;
--- Comment #2 from ubizjak at gmail dot com 2007-06-28 08:14 ---
(In reply to comment #1)
This bug could be hidden in 4.3.0 as we use MIN_EXPR and MAX_EXPR here.
To clear the typo - we use MIN_EXPR and MAX_EXPR in 4.3.0.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32533
--
rguenth at gcc dot gnu dot org changed:
What|Removed |Added
CC||rguenth at gcc dot gnu dot
|
