From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-3.3 required=5.0 tests=MAILING_LIST_MULTI,
	RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham
	autolearn_force=no version=3.4.4
Received: (qmail 6813 invoked from network); 13 May 2020 18:50:55 -0000
Received: from mother.openwall.net (195.42.179.200)
  by inbox.vuxu.org with ESMTPUTF8; 13 May 2020 18:50:55 -0000
Received: (qmail 30695 invoked by uid 550); 13 May 2020 18:50:53 -0000
Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm
Precedence: bulk
List-Post: <mailto:musl@lists.openwall.com>
List-Help: <mailto:musl-help@lists.openwall.com>
List-Unsubscribe: <mailto:musl-unsubscribe@lists.openwall.com>
List-Subscribe: <mailto:musl-subscribe@lists.openwall.com>
List-ID: <musl.lists.openwall.com>
Reply-To: musl@lists.openwall.com
Received: (qmail 30677 invoked from network); 13 May 2020 18:50:53 -0000
Date: Wed, 13 May 2020 14:50:40 -0400
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
Message-ID: <20200513185040.GY21576@brightrain.aerifal.cx>
References: <CACq8dh2nk9+DZ-wwvF3q66eW4Dd7CbKjFDfXvx22ize4E6Zv_Q@mail.gmail.com>
 <20200512212127.GQ21576@brightrain.aerifal.cx>
 <5ae8c7fa-aed9-d957-fe53-68eb2fa622a6@ludd.ltu.se>
 <CACq8dh0=ojyQfVFs012OVGQkortEoK6RQ9QGoR3exMJk_eS4bw@mail.gmail.com>
 <20200513172718.GW21576@brightrain.aerifal.cx>
 <CACq8dh0YvtV+kuyt4efpM_VjYufhDLbJLqVYvub2CQTZi8kytw@mail.gmail.com>
 <20200513180451.GX21576@brightrain.aerifal.cx>
 <CACq8dh00uxgCd4mxEtRgBL8W975e6Cq_GUeSsqFfRY=VNrpJLQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CACq8dh00uxgCd4mxEtRgBL8W975e6Cq_GUeSsqFfRY=VNrpJLQ@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [musl] Re: [Pcc] [musl] 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@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