From: Anders Magnusson <ragge@ludd.ltu.se>
To: Rich Felker <dalias@libc.org>,
John Arnold <iohannes.eduardus.arnold@gmail.com>
Cc: musl@lists.openwall.com, pcc@lists.ludd.ltu.se
Subject: [musl] Re: [Pcc] [musl] PCC unable to build musl 1.2.0 (and likely earlier)
Date: Wed, 13 May 2020 09:10:40 +0200 [thread overview]
Message-ID: <5ae8c7fa-aed9-d957-fe53-68eb2fa622a6@ludd.ltu.se> (raw)
In-Reply-To: <20200512212127.GQ21576@brightrain.aerifal.cx>
Den 2020-05-12 kl. 23:21, skrev Rich Felker:
> Thanks. Adding pcc list to cc.
>
> On Tue, May 12, 2020 at 03:59:36PM -0500, John Arnold wrote:
>> With an i386 PCC 1.2.0.DEVEL built from source from
>> http://pcc.ludd.ltu.se/ftp/pub/pcc/pcc-20200510.tgz, I was unable to
>> build an i386 musl 1.2.0. The compiler first hits this error:
>>
>> ../include/limits.h:10: error: bad charcon
>>
>> This line was the only change made in commit cdbbcfb8f5d, but it has a
>> lengthy commit message about the proper way of determining CHAR_MIN
>> and CHAR_MAX.
> I think this is clearly a PCC bug, one they can hopefully fix. The
> commit message cites the example from 6.4.4.4:
Can you please sen med the offending line?
>> Reverting that change fixes the issue with limits.h, but PCC then runs
>> into another problem:
>>
>> src/complex/catan.c, line 105: operands of = have incompatible types
>> src/complex/catan.c, line 105: cannot recover from earlier errors: goodbye!
> Are there any warnings before this? Perhaps pcc is not aware of
> __builtin_complex and treating it as an implicit declaration of a
> function returning int? But then int should still convert to complex
> double just fine, so I think the problem is just a weird bug in PCC
> with complex types.
Same here, can you send me the line that causes the bug?
And true, __builtin_complex is not recognized in pcc.
>> Undoing this change results in hitting yet more errors:
>> /tmp/ctm.AkDmnc: Assembler messages:
>> /tmp/ctm.AkDmnc:50: Error: bad register name `%%ax'
> Which file is this in? I think it's inline asm expanded from
> somewhere, maybe the new x86 math functions, and it might be something
> we're doing not quite right or a PCC bug. We could suppress the asm
> with pcc (or with a configure test for the bug) if it's not something
> they can fix.
Pcc recognizes gcc extended assembler, but it is more strict than gcc so
it sometimes
reveals bugs that gcc don't catch.
...and same here, please send me what fails so that I can fix the bugs :-)
-- R
next prev parent reply other threads:[~2020-05-13 7:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 20:59 John Arnold
2020-05-12 21:21 ` Rich Felker
2020-05-13 7:10 ` Anders Magnusson [this message]
2020-05-13 14:30 ` [musl] Re: [Pcc] " Rich Felker
2020-05-13 19:09 ` Anders Magnusson
2020-05-13 19:33 ` Rich Felker
2020-05-13 20:31 ` Anders Magnusson
2020-05-13 21:49 ` Rich Felker
2020-05-13 17:00 ` John Arnold
2020-05-13 17:27 ` Rich Felker
2020-05-13 17:53 ` John Arnold
2020-05-13 18:04 ` Rich Felker
2020-05-13 18:49 ` John Arnold
2020-05-13 18:50 ` Rich Felker
2020-05-15 0:24 ` John Arnold
2020-05-13 19:36 ` Anders Magnusson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5ae8c7fa-aed9-d957-fe53-68eb2fa622a6@ludd.ltu.se \
--to=ragge@ludd.ltu.se \
--cc=dalias@libc.org \
--cc=iohannes.eduardus.arnold@gmail.com \
--cc=musl@lists.openwall.com \
--cc=pcc@lists.ludd.ltu.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).