[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140813144326.GM5170@example.net>
Date: Wed, 13 Aug 2014 16:43:26 +0200
From: u-igbb@...ey.se
To: musl@...ts.openwall.com
Subject: Re: compiling musl on x86_64 linux with pcc
On Wed, Aug 13, 2014 at 10:23:32AM -0400, Rich Felker wrote:
> > 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
> met.
I suspected this, did not try to run that code.
> I think tcc has a long ways to go... But pcc was working in the past
> (at least on 32-bit) and should work.
I'll report the progress when I come further.
> 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.
Anders wrote:
>> __syscall(
>> #ifdef SYS_mmap2
>>
>> becomes after -E
>>
>> __syscall(#ifdef SYS_mmap2 ....
>Having conditionals inside macro lists is undefined, see 6.10.3 clause 11.
>Here I recommend fixing the code instead.
I think this means the code should be changed.
Regards,
Rune
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.
