[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <52F7F8C0.9070607@gentoo.org>
Date: Sun, 09 Feb 2014 22:53:04 +0100
From: Luca Barbato <lu_zero@...too.org>
To: musl@...ts.openwall.com
Subject: Re: Musl + TCC
On 09/02/14 22:43, Rich Felker wrote:
> On Sun, Feb 09, 2014 at 09:15:28PM +0100, Daniel Cegiełka wrote:
>> 2014-02-09 21:07 GMT+01:00 Andre Renaud <andre@...ewatersys.com>:
>>> Hi,
>>> Has anyone had a go at building musl with Tiny-CC http://bellard.org/tcc/?
>>
>> and libfirm/cparser? :)
>> http://pp.ipd.kit.edu/firm/
>
> If I remember correctly, last I checked, libfirm/cparser was working
> fine for static linking, but did not support dynamic linking (it
> completely lacked position-independent code generation, i.e. -fPIC).
> There were some problems with complex and some floating point things,
> but I think they were all fixed. I built a static libc.a with cparser
> and the results passed basic testing.
>
> This is definitely the most promising GCC-alternative compiler I've
> seen, so if anybody's up for helping promote it and/or contribute to
> the project, that would be great.
I contributed a bit and I'm routinely filling bugs to it.
It is indeed easy to work with and the upstream developers are pleasant
to work with.
They indeed need more mindshare. I hope once they converted cparser to
an usable library they'll bloom fully.
lu
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.
