public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
* null reference function pointer check on __register_frame_info() within frame_dummy() in crtstuff.c
@ 2019-11-29 21:57 William Tambe
  0 siblings, 0 replies; only message in thread
From: William Tambe @ 2019-11-29 21:57 UTC (permalink / raw)
  To: gcc-help

Is there a way to prevent GCC from generating null reference function pointers ?

In fact, the target to which I ported GCC always generate
position-independent-code; so it is not always loaded at the address
specified in the ELF header, and that is where I run into issues with
the way GCC implement null reference function pointers.

For example in crtstuff.c, there is a null reference function pointer
check on __register_frame_info() within frame_dummy(); if the
executable is not loaded at the address specified in the ELF header,
the check on __register_frame_info() is never null when it is supposed
to be null.

Is there a way to prevent GCC from generating null reference function pointers ?

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2019-11-29 21:57 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-11-29 21:57 null reference function pointer check on __register_frame_info() within frame_dummy() in crtstuff.c William Tambe

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).