http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21305
Richard Guenther changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|
--- Additional Comments From schlie at comcast dot net 2005-05-19 03:55
---
(In reply to comment #0)
> The current -fdelete_null_pointer_checks implementation makes assumptions that
> the target processor will trap on reads or writes to address zero.
> Unfortunately,
> these assumption
--
What|Removed |Added
OtherBugsDependingO||21479
nThis||
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21305
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-04-30
21:19 ---
Note the flag is old, it comes from:
Thu Sep 23 13:55:21 1999 Jeffrey A Law ([EMAIL PROTECTED])
* invoke.texi: Document -fdelete-null-pointer-checks
* toplev.c (flag_delete_null_po
--- Additional Comments From roger at eyesopen dot com 2005-04-30 21:18
---
Apparently the behaviour of this code is undefined in the C/C++ language
standards, though this transformation is performed in front-end independent
code. Perhaps its only a quality of implementation issue.
--
--
What|Removed |Added
Component|tree-optimization |middle-end
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21305
