From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gcc-patches-return-46396-listarch-gcc-patches=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 26902 invoked by alias); 21 Nov 2001 05:34:49 -0000
Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc-patches/>
List-Post: <mailto:gcc-patches@gcc.gnu.org>
List-Help: <mailto:gcc-patches-help@gcc.gnu.org>
Sender: gcc-patches-owner@gcc.gnu.org
Received: (qmail 26866 invoked from network); 21 Nov 2001 05:34:48 -0000
Received: from unknown (HELO geoffk.org) (67.166.30.54)
by sourceware.cygnus.com with SMTP; 21 Nov 2001 05:34:48 -0000
Received: (from geoffk@localhost)
by geoffk.org (8.9.3/8.9.3) id VAA13467;
Tue, 20 Nov 2001 21:33:46 -0800
Date: Tue, 13 Nov 2001 15:03:00 -0000
Message-Id: <200111210533.VAA13467@geoffk.org>
X-Authentication-Warning: localhost: geoffk set sender to geoffk@geoffk.org using -f
From: Geoff Keating <geoffk@geoffk.org>
To: dje@watson.ibm.com
CC: shebs@apple.com, obrien@FreeBSD.org, gcc-patches@gcc.gnu.org
In-reply-to: <200111210519.AAA14762@makai.watson.ibm.com> (message from David
Edelsohn on Wed, 21 Nov 2001 00:19:25 -0500)
Subject: Re: [PATCH] adds powerpc-*-freebsd? to mainline
Reply-to: Geoff Keating <geoffk@redhat.com>
References: <200111210519.AAA14762@makai.watson.ibm.com>
X-SW-Source: 2001-11/txt/msg00716.txt.bz2
> cc: shebs@apple.com, obrien@FreeBSD.org, gcc-patches@gcc.gnu.org
> Date: Wed, 21 Nov 2001 00:19:25 -0500
> From: David Edelsohn <dje@watson.ibm.com>
>
> >>>>> Geoff Keating writes:
>
> Geoff> Why do you object?
>
> Because a FreeBSD maintainer for any architecture now can break
> all PowerPC ELF targets.
Well,
(a) so let's tell them not to do that.
(b) I really don't think it's likely that they'll be able to somehow
break things in a file that defines five macros, unless
of course they forget to 'cvs add' it (hint hint David)
(c) and anyway, the automated regression tester will catch them.
> Not to mention that this is ugly and cumbersome.
I couldn't think of a better solution, neither could David, and I
find the solution grows on me. Isn't this exactly what header files
are for?
--
- Geoffrey Keating <geoffk@geoffk.org> <geoffk@redhat.com>