[cfe-dev] [LLVMdev] [RFC PATCH] X32 ABI support for Clang/compiler-rt

[Steven Newbury]

On Thu, 2013-08-22 at 11:31 +0400, Alexey Samsonov wrote:
> On Thu, Aug 22, 2013 at 11:23 AM, Steven Newbury <steve at snewbury.org.uk>wrote:
> 
> > On Wed, 2013-08-21 at 23:59 -0700, Dmitri Gribenko wrote:
> > > On Wed, Aug 21, 2013 at 11:04 PM, Steven Newbury <steve at snewbury.org.uk>
> > wrote:
> > > > I've been trying
> > > > to get x32 ABI support working in Clang and compiler-rt, I based off
> > the
> > > > previous clang patch, bringing it up to date with the changes in trunk,
> > > > and hacked together handling of x32 "ARCH" support for compiler-rt.
> > > > (there must be a better way??)
> > >
> > > If you are just trying to get basic things working, you don't need to
> > > port compiler-rt immediately.  It is still pretty important (for
> > > example, to support features like Address Sanitizer), but not critical
> > > -- you will still get a useable Clang without building compiler-rt.
> > >
> > > Dmitri
> > >
> >
> > Having Clang working would of course be my primary goal, that said,
> > being able to compile compiler-rt is a pretty good test all is working
> > as it should be! :)  It's also built/installed as part of the Gentoo
> > llvm ebuild when the clang useflag is enabled, so from that point of
> > view, I need to get it working.
> >
> 
> I see, but it's not really good to build the libraries that are not
> expected to work...I think you
> should instead detect x32 host in the makefiles and avoid buidling
> compiler-rt libraries in that case.
> 
Certainly, if I can get to the point of a working Clang, but I find the
libraries are beyond my current ability to port, it might well be worth
making available what does work.  But right now this is only building on
my local chroot, with the intention of then pushing it to my
experimental x32 portage overlay once I have something worth testing.