--- Comment #9 from ubizjak at gmail dot com 2009-09-17 09:40 ---
(In reply to comment #5)
32bit HWI cannot represent 128bit constants. If you are lucky and it works as
far as creating code you should not be surprised that some constants might
be forced to memory. The only chance
--- Comment #8 from hp at gcc dot gnu dot org 2009-04-08 06:06 ---
(In reply to comment #6)
Then we should fix this bug by requiring 64-bit HOST_WIDE_INT for x86 targets
This is just the special case of GCC generating different code for the same
target from different *hosts*; you'd
--- Comment #7 from info dot gnu at rt-labs dot com 2009-04-07 16:52
---
*** Bug 39663 has been marked as a duplicate of this bug. ***
--
info dot gnu at rt-labs dot com changed:
What|Removed |Added
--- Comment #3 from rguenth at gcc dot gnu dot org 2008-03-06 09:43 ---
Indeed. Maybe we should finally change the default.
--
rguenth at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #6 from jsm28 at gcc dot gnu dot org 2008-03-06 13:51 ---
Then we should fix this bug by requiring 64-bit HOST_WIDE_INT for x86 targets
rather than by declaring it will never be fixed. It can be closed when we've
switched to 64-bit HOST_WIDE_INT (or as a duplicate if we
--- Comment #4 from jsm28 at gcc dot gnu dot org 2008-03-06 13:32 ---
Different code for the same target on different hosts is a valid bug, not
INVALID. If a target works with more than one HOST_WIDE_INT setting, the
choice should not affect the code generated; this is separate from
--- Comment #5 from rguenth at gcc dot gnu dot org 2008-03-06 13:38 ---
32bit HWI cannot represent 128bit constants. If you are lucky and it works as
far as creating code you should not be surprised that some constants might
be forced to memory. The only chance to generate the same
--- Comment #1 from hjl dot tools at gmail dot com 2008-03-05 04:27 ---
The difference comes from tree_expand_cfg pass:
[EMAIL PROTECTED] stage1-gcc]$ diff -up 32/x.i.132r.expand 64
--- 32/x.i.132r.expand 2008-03-04 20:25:21.0 -0800
+++ 64/x.i.132r.expand 2008-03-04
--- Comment #2 from pinskia at gcc dot gnu dot org 2008-03-05 07:49 ---
This is a HWI issue. I don't know how many times I tell people that x86 should
default to 64bit HWI if it uses TImode.
--
pinskia at gcc dot gnu dot org changed:
What|Removed
--
steven at gcc dot gnu dot org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Last
10 matches
Mail list logo
