From: Rich Felker <dalias@aerifal.cx>
To: John Arnold <iohannes.eduardus.arnold@gmail.com>
Cc: Anders Magnusson <ragge@ludd.ltu.se>,
musl@lists.openwall.com, pcc@lists.ludd.ltu.se
Subject: Re: [musl] Re: [Pcc] [musl] PCC unable to build musl 1.2.0 (and likely earlier)
Date: Wed, 13 May 2020 14:50:40 -0400 [thread overview]
Message-ID: <20200513185040.GY21576@brightrain.aerifal.cx> (raw)
In-Reply-To: <CACq8dh00uxgCd4mxEtRgBL8W975e6Cq_GUeSsqFfRY=VNrpJLQ@mail.gmail.com>
On Wed, May 13, 2020 at 01:49:22PM -0500, John Arnold wrote:
> On Wed, May 13, 2020 at 1:04 PM Rich Felker <dalias@aerifal.cx> wrote:
> > That doesn't sound related. %%ax appearing in the input to the
> > assembler would always indicate a bug in either the compiler or the
> > inline asm text in the program being compiled.
>
> I did some poking around with pcc -S and it looked like %%ax was only
> appearing in the context of the fnstsw instruction, which in pcc's
> source only occurs once, in line 329 of arch/i386/local2.c:
>
> expand(p, 0, "\tfnstsw %%ax\n");
>
> My assembly is *really* basic, so I don't know what that means, but
> hopefully it's relevant?
It just means someone inadvertently wrote %% thinking the expected
form was inline-asm text that would be %-expanded rather than whatever
form PCC uses at this point where all %'s are literal. Changing it to
a single % should fix it.
Rich
next prev parent reply other threads:[~2020-05-13 18:50 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 ` [musl] Re: [Pcc] " Anders Magnusson
2020-05-13 14:30 ` 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 [this message]
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=20200513185040.GY21576@brightrain.aerifal.cx \
--to=dalias@aerifal.cx \
--cc=iohannes.eduardus.arnold@gmail.com \
--cc=musl@lists.openwall.com \
--cc=pcc@lists.ludd.ltu.se \
--cc=ragge@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).