Defeat compiler optimization which assumes function addresses are never NULL

Kevin Day thekevinday at gmail.com
Thu Sep 29 04:16:09 UTC 2011


For the commit http://git.uclibc.org/uClibc/commit/?id=82f8d0bce10403deab704871e638edc24e7933ee

Would it be better to pass "-fno-delete-null-pointer-checks"?
I suspect that is the optimization issue, but I could easily be wrong.

gcc documentation has the following about that option:
-fdelete-null-pointer-checks
    "Assume that programs cannot safely dereference null pointers, and
that no code or data element resides there."
 ...

-- 
Kevin Day


More information about the uClibc mailing list