This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: libio / gen-params and __printf_fp test
- To: David Korn <dkorn at pixelpower dot com>
- Subject: Re: libio / gen-params and __printf_fp test
- From: Per Bothner <per at bothner dot com>
- Date: 09 Feb 2001 23:43:53 -0800
- Cc: "Gcc-List (E-mail)" <gcc at gcc dot gnu dot org>
- References: <718D38CAB6E0D011B2C90060970C28A564268F@EXCHANGESERVER>
David Korn <dkorn@pixelpower.com> writes:
> Your name is at the top of this file, so I thought I'd ask you about
> one of the tests in it, lines 712-725 (in 2.95.2 release, and probably
> the same in 2.95.3)
> -------------------------------------------------------------------------
> # A little test program to check if __printf_fp is available.
I don't remember this particular test - it may be after my time.
> Now, on the cross-target I'm developing for (powerpc-wrs-vxworks),
> we don't have printf_fp. But this test still sets the defines to 1. This
> is because under vxworks, we always compile with the linker -r flag; the
> C runtime lib. is build into the OS and dynamically linked into our
> applications at runtime.
Yes, I remember these kinds of problems with vxworks. I consider it
a bug in vxworks's linker (a linker could still check for undefined
symbols, except for the ones built in), be you're stuck with it.
I vaguely remember we had some hooks to override the tests on
specific targets, but I don't remember how, and in any it has
probably all changed by now, or it will libstdc++ v3.
--
--Per Bothner
per@bothner.com http://www.bothner.com/~per/