[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200513185040.GY21576@brightrain.aerifal.cx>
Date: Wed, 13 May 2020 14:50:40 -0400
From: Rich Felker <dalias@...ifal.cx>
To: John Arnold <iohannes.eduardus.arnold@...il.com>
Cc: Anders Magnusson <ragge@...d.ltu.se>, musl@...ts.openwall.com,
pcc@...ts.ludd.ltu.se
Subject: Re: Re: [Pcc] PCC unable to build musl 1.2.0 (and
likely earlier)
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@...ifal.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
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.
