This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [3.1-branch PATCH] fix mips CPP size specs for MEABI.
- From: Mark Mitchell <mark at codesourcery dot com>
- To: "cgd at broadcom dot com" <cgd at broadcom dot com>, "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>
- Cc: "echristo at redhat dot com" <echristo at redhat dot com>, "aoliva at gcc dot gnu dot org" <aoliva at gcc dot gnu dot org>
- Date: Fri, 26 Apr 2002 11:13:18 -0700
- Subject: Re: [3.1-branch PATCH] fix mips CPP size specs for MEABI.
- References: <yov5y9fatjxj.fsf@broadcom.com>
> Verified that w/ this patch the compiler & libstdc++-v3 builds for
> target mipsisa32-elf, host sparc solaris.
Is this build failure a regression? (Probably from GCC 2.95?)
If so, we must apply your patch, and it is approved.
I am relieved to see that your patch only touches systems where O64 is
the default; those are relatively rare.
A meta-question: the compiler knows what size_t is, and now the compiler
and preprocessor are cooperative, so why do we have to put this stuff
in the specs at all? I know the answer: stand-alone cpplib. But that
just suggests that we should get this information into cpplib, and then
not have it separately in the compiler. There's no reason that one half
of the toolchain can't learn the value from the other half, fixing all
these bugs once and for all.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com