This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [3.0 critical] Make fixproto deal with assert.h
- To: Mark Mitchell <mark at codesourcery dot com>, gcc-patches at gcc dot gnu dot org
- Subject: Re: [3.0 critical] Make fixproto deal with assert.h
- From: Zack Weinberg <zackw at stanford dot edu>
- Date: Thu, 10 May 2001 13:58:19 -0700
Mark Mitchell writes:
> Going one step further -- do we need to be in the business of
> providing <assert.h> at all, even on "old old" targets? We don't
> provide the C library, and <assert.h> is not part of the
> language-support library provided by the compiler -- it's not like
> math emulation or <limits.h>, for example.
<assert.h> is used in several of the non-C front ends and language
runtimes. I could certainly go through and change them all to if/abort
pairs. It'd be a lot more invasive, but it would allow us to get rid of
__eprintf, so it might be worth it.
Or I could get rid of assert.h and not bother changing its users. Autoconf
uses assert.h unconditionally in AC_CHECK_FUNC and no one's complained --
suggests that it's near-universal on systems people actually care about.
What would you prefer?
zw