From owner-freebsd-arch@FreeBSD.ORG  Tue Feb 16 21:07:41 2010
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: arch@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 583201065672;
	Tue, 16 Feb 2010 21:07:41 +0000 (UTC) (envelope-from imp@bsdimp.com)
Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85])
	by mx1.freebsd.org (Postfix) with ESMTP id 1843A8FC19;
	Tue, 16 Feb 2010 21:07:41 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
	by harmony.bsdimp.com (8.14.3/8.14.1) with ESMTP id o1GKwqVC035119;
	Tue, 16 Feb 2010 13:58:53 -0700 (MST) (envelope-from imp@bsdimp.com)
Date: Tue, 16 Feb 2010 13:59:06 -0700 (MST)
Message-Id: <20100216.135906.812628220523048669.imp@bsdimp.com>
To: attilio@FreeBSD.org
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <3bbf2fe11002151610l41526f55r5e60b5e46ce42b64@mail.gmail.com>
References: <3bbf2fe11002151610l41526f55r5e60b5e46ce42b64@mail.gmail.com>
X-Mailer: Mew version 6.3 on Emacs 22.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: arch@FreeBSD.org, emaste@sandvine.com
Subject: Re: [PATCH] Adding shared code support for ia32 and amd64 -- x86
 sub-branch
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Feb 2010 21:07:41 -0000

In message: <3bbf2fe11002151610l41526f55r5e60b5e46ce42b64@mail.gmail.com>
            Attilio Rao <attilio@FreeBSD.org> writes:
: There are few things to discuss. One, that I had not necessity to dig
: about still, is about how to organize headers (include/). Maybe some
: replication ala pc98 may be good.

Most of the pc98 replication these days is in the form of "#include
<i386/foo.h>" and we install i386/include into /usr/include/i386 as
well as pc98/include into /usr/include/machine.

I'm working in a similar vein.  For a while, one has had to specify
TARGET_BIG_ENDIAN in order to build big endian MIPS or ARM binaries.
This is lame.  I've eliminated it and have made it possible to build
mipsel, mipseb, arm or armeb binaries by setting TARGET_ARCH to one of
these, while still sharing all the mips code in one directory and all
the arm code in another.

Warner