--
bonzini at gnu dot org changed:
What|Removed |Added
CC||bonzini at gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32653
--- Comment #3 from bonzini at gnu dot org 2007-09-24 12:39 ---
CCing resident memory-hog bug killer.
--
bonzini at gnu dot org changed:
What|Removed |Added
--- Comment #8 from bonzini at gnu dot org 2007-04-02 16:22 ---
... because GCC now has -mpc to limit precision for float/double operations.
Even as far as x86 is concerned, this is a "special case" of PR323, and thus
I'm closing it as fixed.
--
bonzini at gnu
--- Comment #7 from bonzini at gnu dot org 2007-04-02 16:21 ---
Reopened...
--
bonzini at gnu dot org changed:
What|Removed |Added
Status|RESOLVED
--- Comment #94 from bonzini at gnu dot org 2007-04-02 16:20 ---
I think that Uros' patch to add a -mpc switch for precision control would "fix"
this.
The real fix would be to automatically insert fldcw instructions before
float/double operations, in order to limit the p
--- Comment #11 from bonzini at gnu dot org 2006-04-18 15:20 ---
... but then anyway the bug pops up in reload. So it is definitely the same
bug as PR24230, and here is a modified version of the PR24230 testcase:
/* Compile with -O2 -maltivec */
#define REGLIST
--- Comment #10 from bonzini at gnu dot org 2006-04-18 14:39 ---
It's probably two different bugs, since the 4.1 bug is in loop.c. We need to
add a can_assign_to_reg_p call before creating a movable.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27158
--- You are rece
--- Comment #9 from bonzini at gnu dot org 2006-04-18 14:29 ---
The mem is for a
(const_vector:V4SF [
(const_double:SF -NaN [-NaN])
(const_double:SF -NaN [-NaN])
(const_double:SF -NaN [-NaN])
(const_double:SF -NaN [-NaN])
])
--
http
--- Comment #8 from bonzini at gnu dot org 2006-04-18 13:47 ---
Seems similar to PR24230, but cannot be fixed really in the same way.
--
bonzini at gnu dot org changed:
What|Removed |Added
9 matches
Mail list logo
