This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
RE: [PATCH 2.95.3 - WITHDRAWN] Fix powerpc-wrs-vxworks eabi backwards incompatibility.
- To: David Korn <dkorn at pixelpower dot com>
- Subject: RE: [PATCH 2.95.3 - WITHDRAWN] Fix powerpc-wrs-vxworks eabi backwards incompatibility.
- From: Bernd Schmidt <bernds at redhat dot com>
- Date: Wed, 13 Dec 2000 15:57:06 +0000 (GMT)
- Cc: "Gcc-Patches (E-mail)" <gcc-patches at gcc dot gnu dot org>,"David Edelsohn (E-mail)" <dje at watson dot ibm dot com>,"Mike Stump (E-mail)" <mrs at windriver dot com>,"'Geoff Keating'" <geoffk at geoffk dot org>
On Wed, 13 Dec 2000, David Korn wrote:
> You sound as if you've made your mind up, and the decision rests with you,
> of course. But which questions are still open?
Questions such as the one below (-m switch vs. target name), and I also
believe the question of whether we actually want to support the older ABI
in the compiler at all hasn't entirely been resolved. This is up to the
PPC maintainers in the end.
Quite apart from that, I'd prefer to be entirely sure that these patches will
fix all binary compatibility problems. We wouldn't want to get into a
situation where we promise working support for this target in 2.95.3, only
to find out that there are still glitches and users demand a 2.95.4 release.
If we decide to provide support for this, let's get it into the development
sources first, not try to rush it into an upcoming release.
> However I wasn't planning to post them until I'd run the testsuite, which
> will probably not be until over the weekend (I need to buy new hardware and
> set up a remote test server). So what's the timescale you envisage for the
> 2.95.3 release?
The deadline for submitting patches is Dec 17.
Bernd