This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: use of ifndef inhibit_libc to disable the contents linux-unwind.h for targets with MD_UNWIND_SUPPORT
- From: Daniel Jacobowitz <drow at false dot org>
- To: gcc at gcc dot gnu dot org
- Date: Mon, 27 Aug 2007 16:35:33 -0400
- Subject: Re: use of ifndef inhibit_libc to disable the contents linux-unwind.h for targets with MD_UNWIND_SUPPORT
- References: <46D33423.1060506@ou.edu>
On Mon, Aug 27, 2007 at 03:29:23PM -0500, Stephen M. Kenton wrote:
> As seen below, the Linux targets which use glibc define MD_UNWIND_SUPPORT and
> have
> a customized linux-unwind.h file. However, mips and i386 start and end those
> files with
> #ifndef inhibit_libc .... #endif statements which disable the entire contents
> of the file if inhibit_libc is set.
> Those are the only two such targets I can successfully build with inhibit_libc
> without the use of enable-sjlj-exceptions.
> Is there some reason that every instance of linux-unwind.h should not start and
> end with those same
> #ifndef inhibit_libc ... #endif statements? Or, alternatively, should setting
> of inhibit_libc force
> a #undef MD_UNWIND_SUPPORT at some suitably central place rather than doing
> things the
> way that mips and i386 currently handle it?
FWIW, I've come to the opinion that we should just copy the relevant
structure layouts from glibc into gcc and avoid this problem. If the
layout ever changes, we're going to need to handle both in gcc anyway.
--
Daniel Jacobowitz
CodeSourcery