Date: Thu, 17 Apr 2014 14:50:11 -0600 From: Ian Lepore <ian@FreeBSD.org> To: Mark R V Murray <mark@grondar.org> Cc: Tim Kientzle <tim@kientzle.com>, freebsd-arm <freebsd-arm@FreeBSD.org>, ticso@cicely.de Subject: Re: Building an ARM/RPI-B release (hacked) on CURRENT/AMD64. Message-ID: <1397767811.1124.289.camel@revolution.hippie.lan> In-Reply-To: <54D788B2-BD68-4F75-86FF-0C4E71D9B75A@grondar.org> References: <9FDD6F0E-B2A9-48D9-A3E4-181868995FDA@grondar.org> <EC41E53F-96EF-4652-9A02-D49448D104BE@kientzle.com> <20140417103117.GE44138@cicely7.cicely.de> <1397738961.1124.157.camel@revolution.hippie.lan> <ED243420-AC33-4D90-A23D-0266C142F3C1@grondar.org> <1397761628.1124.245.camel@revolution.hippie.lan> <7196A020-54E1-42FA-B8A0-25B145B0E412@bsdimp.com> <54D788B2-BD68-4F75-86FF-0C4E71D9B75A@grondar.org>
index | next in thread | previous in thread | raw e-mail
On Thu, 2014-04-17 at 20:54 +0100, Mark R V Murray wrote: > On 17 Apr 2014, at 20:14, Warner Losh <imp@bsdimp.com> wrote: > > > > > On Apr 17, 2014, at 1:07 PM, Ian Lepore <ian@FreeBSD.org> wrote: > >> > >> Hmmm. After a bit of poking around in the llvm code, it looks like the > >> full extent of the support for -ffixed-r9 is that it doesn't consider > >> that register available for use by the code generator; that's only part > >> of what u-boot needs. > > > > what’s the other part? Global register variables like this? > > Yah. U-boot/Arm is heavily dependant on using R9 (previously R8) as a > global register variable. > > >> Some online notes I found for clang 3.5 claim that global register > >> variables aren't supported, and aren't likely to be any time soon. > > > > Is that a poke in the eye of uboot, or is it more of a contention that > > uboot is moving away from that need? > > It means that for now I guess we are stuck with using GCC to compile u-boot. > > I’d mind a lot less if this was done as a port. > > <thinking mode=“aloud”> > Hmm. A port to do what crochet does, without all the FreeBSD/ARM (build|install)(world|kernel) stuff? > > Something that makes an empty <mumble>.img (with only the weird boot bits in it) as its “product” for later use by the release process might be nice. > > I’m guessing (more like hoping) that once the boot bits work, they’ll be pretty stable for a given platform for a while, and the .img file could be kept under src/release/… somewhere. This way, it doesn’t matter if some humongous GCC port is used for cross-building; this would be only needed when the boot-bits change. > <thinking> I'm not very familiar with crochet, but I'm confused now... Tim K. is the creator of crochet, and he's the maintainer of the u-boot-beaglebone-eabi port, which uses the gcc cross-compiler from ports. So did Tim not use his own excellent port in crochet? -- Ianhelp
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1397767811.1124.289.camel>