http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30255
Jackie Rosen changed:
What|Removed |Added
CC||jackie.rosen at hushmail dot
com
--- Comm
--- Comment #11 from rguenth at gcc dot gnu dot org 2006-12-27 16:21
---
Just to mention it - you can use 'long double' to force 80bit spills.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30255
--- Comment #10 from whaley at cs dot utsa dot edu 2006-12-19 17:18 ---
Guys,
In the interests of full disclosure, I did some quick timings on the Core2Duo,
and as I kind of suspected, scalar SSE crushed x87 there. I was pretty sure
scalar SSE could achieve 2 flop/cycle, while Intel ke
--- Comment #9 from whaley at cs dot utsa dot edu 2006-12-19 16:04 ---
Ian,
Thanks for the info. I see I failed to consider the cross-register moves you
mentioned. However, can't those be moved through memory, where something
destined for a 64-bit register is first written from the 80
--- Comment #8 from ian at airs dot com 2006-12-19 14:57 ---
I think I agree that if we spill an 80387 register to the stack, and then load
the value back into an 80387 register, that we should spill all 80 bits, rather
than implicitly converting to DFmode or SFmode.
This would unfortun
--- Comment #7 from whaley at cs dot utsa dot edu 2006-12-19 00:31 ---
>Depends on what you mean by fixable by the programmer because most people don't
know anything about precusion issues.
Most people don't know programming at all, so I guess you are suggesting that
errors that are f
--- Comment #6 from pinskia at gcc dot gnu dot org 2006-12-18 23:02 ---
>I cannot, of course, force you to admit it, but 323 is a bug fixable by the
> programmer, and this one is not.
Depends on what you mean by fixable by the programmer because most people don't
know anything about pr
--- Comment #5 from whaley at cs dot utsa dot edu 2006-12-18 22:14 ---
I cannot, of course, force you to admit it, but 323 is a bug fixable by the
programmer, and this one is not. The other requires a lot of work in the
compiler, and this does not. So, viewing them as the same can be d
--- Comment #4 from pinskia at gcc dot gnu dot org 2006-12-18 22:04 ---
The problem with register spilling and what PR 323 is talking about is all the
same issue really, it is just exposed differently.
*** This bug has been marked as a duplicate of 323 ***
--
pinskia at gcc dot gnu
--- Comment #3 from whaley at cs dot utsa dot edu 2006-12-18 21:16 ---
BTW, in case it isn't obvious, here's the fix that I typically use for problems
like bug 323 that I cannot when it is gcc itself that is unpredictably spilling
the computation:
void test(double x, double y)
{
const
--- Comment #2 from whaley at cs dot utsa dot edu 2006-12-18 20:43 ---
Hi,
While it may be decided not to fix this problem, this is not a duplicate of bug
323, and so it should be closed for another reason if you want to ignore it.
323 has a problem because of the function call, where
--- Comment #1 from pinskia at gcc dot gnu dot org 2006-12-18 20:16 ---
*** This bug has been marked as a duplicate of 323 ***
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
12 matches
Mail list logo
