Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 13 Aug 2014 10:23:32 -0400
From: Rich Felker <>
Subject: Re: compiling musl on x86_64 linux with ppc

On Wed, Aug 13, 2014 at 02:56:08PM +0200, wrote:
> > > src/aio/aio_readwrite.c, line 23: compiler error: unsupported xasm constraint r11
> > > error: XXXXX/libexec/ccom terminated with status 1
> > > make: *** [src/aio/aio_readwrite.o] Error 1
> > > -----------
> > > 
> > > Is there any way around this, short of adding the register assignment
> > > functionality to the compiler?
> > 
> > Just use the #ifdef __clang__ branch of the code which handles the
> > same brokenness in clang. :-)
> According to Anders Magnusson (he replied on pcc-list) it is sufficient
> to refer to r11 as %r11 to make it work. He thinks otherwise of adding
> the alias r11 for %r11 in pcc.
> Indeed, with a change of all "r11" to "%r11" in
>  arch/x86_64/syscall_arch.h
> the compilation went through without disabling the separate __syscallN().

Just because it compiled doesn't mean it works. Those warnings about
register assignment definitely should be hard errors because the code
will do horribly wrong things if the requested constraints are not

> My goal is a musl-based selfcontained pcc toolchain.
> I'd like to also have a tcc-based one but musl seems to be too hard
> a target for tcc yet :( sigh.

I think tcc has a long ways to go... But pcc was working in the past
(at least on 32-bit) and should work.

BTW about the mmap2 preprocessor issue, did you raise that with ppc
developers too? I think it's a bug on their side but I'm not 100%
sure. If the code in musl is not valid C I'll change it, but if it is,
I think we should just wait for pcc to get fixed.


Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.