This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug optimization/12092] ICE: Floating point exception
- From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 29 Aug 2003 16:30:25 -0000
- Subject: [Bug optimization/12092] ICE: Floating point exception
- References: <20030828094713.12092.wmertens@gentoo.org>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12092
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed|2003-08-28 13:00:55 |2003-08-29 16:30:24
date| |
------- Additional Comments From pinskia at gcc dot gnu dot org 2003-08-29 16:30 -------
Something here is causing it:
>From loop.c:
4030 /* Prefetch might be worthwhile only when the loads/stores are dense. */
4031 if (PREFETCH_ONLY_DENSE_MEM)
4032 if (density * 256 > PREFETCH_DENSE_MEM * 100
4033 && (info[i].total_bytes / PREFETCH_BLOCK <--- I want to say
this guy is causing it
4034 >= PREFETCH_BLOCKS_BEFORE_LOOP_MIN))
And it is PREFETCH_BLOCK is defined as ix86_cost->prefetch_block which is zero at
this point because we are tuning for i486 (which does not have prefetch at all) but our
arch is pentium4 which does have prefetch so we try to use prefetch but we need to
figure out if it is good to prefetch so we do a divide on PREFETCH_BLOCK but since
PREFETCH_BLOCK is zero here, we get an floating exception.