--
rguenth at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.3.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21059
--- Comment #7 from sje at cup dot hp dot com 2009-02-20 22:36 ---
It looks like this was fixed in the 4.3 time frame so I am closing the defect.
--
sje at cup dot hp dot com changed:
What|Removed |Added
--- Comment #6 from wilson at gcc dot gnu dot org 2005-12-02 19:16 ---
Oops. That patch should have a "| PROP_AUTOINC" in the new update_life_info
call. That would explain why I was seeing some unexpected de-optimizations
with the patch.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi
--- Comment #5 from wilson at gcc dot gnu dot org 2005-12-02 04:12 ---
Created an attachment (id=10387)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=10387&action=view)
Delay auto-inc generation until after determining which regs live across
setjmp.
This is my proposed untested pa
--- Comment #4 from wilson at gcc dot gnu dot org 2005-12-02 02:24 ---
The spurious warning is a problem because binutils is compiled by -Werror by
default now, when compiled by gcc. This spurious warning thus causes a build
failure for binutils. This build failure does not show up in
--
gdr at gcc dot gnu dot org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Last reconfirmed
--- Additional Comments From trt at acm dot org 2005-06-02 18:40 ---
The current warning algorithm is too simple. This would be better:
For each function that contains call(s) to setjmp(), compute:
ref_nz The set of variables that might possibly be live
(reference
--- Additional Comments From schwab at suse dot de 2005-06-01 23:03 ---
The warning is just wrong. There is nothing that can be clobbered by longjmp.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21059
--- Additional Comments From sje at cup dot hp dot com 2005-06-01 22:08
---
It is not clear to me if this bug is about whether or not we should put out the
message or if it is about the format of the message, I.e. that the quotes are
messed up.
--
What|Removed