--- Comment #14 from pinskia at gcc dot gnu dot org 2008-12-12 22:55
---
Subject: Bug 24779
Author: pinskia
Date: Fri Dec 12 22:54:09 2008
New Revision: 142727
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=142727
Log:
2008-12-12 Andrew Pinski
Peter Bergner
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.0.3
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24779
--- Comment #13 from amodra at bigpond dot net dot au 2005-11-18 06:05
---
Fixed
--
amodra at bigpond dot net dot au changed:
What|Removed |Added
Status|NEW
--- Comment #12 from amodra at gcc dot gnu dot org 2005-11-18 05:55 ---
Subject: Bug 24779
Author: amodra
Date: Fri Nov 18 05:55:16 2005
New Revision: 107160
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=107160
Log:
PR target/24779
Backport 2005-03-13 David Ede
--- Comment #11 from amodra at bigpond dot net dot au 2005-11-17 23:38
---
Re comment #8, regression tests passed on powerpc64-linux and powerpc-linux,
with just one regression for ppc64, gcc.c-torture/execute/20020720-1.c
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24779
--- Comment #10 from amodra at bigpond dot net dot au 2005-11-17 23:13
---
Yes, I must have been looking at the wrong set of dumps. On mainline, the
problem of sched1 not seeing a potential mem access via r2 for a fp constant
load only happens now if you compile with -funsafe-math-opti
--- Comment #9 from dje at watson dot ibm dot com 2005-11-17 15:17 ---
Subject: Re: [4.0 Regression] Python miscompilation - TOC reload
"Reliably" is the wrong word. The patch will fix the problem reliably for
the default case; it will not fix it for a particular set of options.
The
--- Comment #8 from amodra at bigpond dot net dot au 2005-11-17 07:17
---
In any case, I think the backporting 4.1 patches won't fix this problem
reliably. I can't see anything that really prevents a similar problem on
mainline, ie. of the first scheduling pass moving some instruction
--- Comment #7 from dje at gcc dot gnu dot org 2005-11-17 00:59 ---
That failure is fixed by the zero_reg_mem predicate changes from March:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/config/rs6000/predicates.md.diff?cvsroot=gcc&r1=1.6&r2=1.7
This is why I didn't want to go down the
--- Comment #6 from amodra at bigpond dot net dot au 2005-11-16 23:58
---
Applying this patch results in a bootstrap failure on powerpc64-linux.
/src/gcc-4.0/gcc/libgcc2.c: In function '__fixtfti':
/src/gcc-4.0/gcc/libgcc2.c:1191: error: unrecognizable insn:
(insn:HI 14 13 15 0 /src/gc
--- Comment #5 from dje at watson dot ibm dot com 2005-11-16 17:45 ---
Subject: Re: Python miscompilation - TOC reload
Appended is a proposed patch to backport the easy_fp_constant
change to 4.0. Can you check if this fixes the problem? This patch may
hurt performance becaus
--
giovannibajo at libero dot it changed:
What|Removed |Added
Summary|Python miscompilation - TOC |[4.0 Regression] Python
|reload
12 matches
Mail list logo
