From: Willy Tarreau <w@1wt.eu>
To: Borislav Petkov <bp@alien8.de>
Cc: Jingbo Xu <jefflexu@linux.alibaba.com>,
tglx@linutronix.de, mingo@redhat.com,
dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [BUG REPORT] arch/x86/include/asm/uaccess_64.h:119: Error: junk at end of line
Date: Sun, 16 Apr 2023 10:36:36 +0200 [thread overview]
Message-ID: <ZDuzlNOmIT0Gd7fF@1wt.eu> (raw)
In-Reply-To: <E8CB02C5-E18C-42F6-93D8-2CC7CB4CB3FF@alien8.de>
Hi Boris,
On Sat, Apr 15, 2023 at 08:56:47PM +0200, Borislav Petkov wrote:
> On April 15, 2023 7:56:01 PM GMT+02:00, Willy Tarreau <w@1wt.eu> wrote:
> >May I send you a cleaner patch for this ?
>
> Can you pls first send a minimal reproducer so that we can show it to gcc folks?
Oh it's not even gcc, it's really just a matter of compatibility with
binutils. Documentation/Changes says binutils minimum is 2.25. This
toolchain I'm using in distcc was made against 2.27, I'm reproducing
the error with it:
$ cat repro.s
.4byte (1U)
.4byte (1UL)
$ /f/tc/x86_64-gcc75_glibc228-linux-gnu/bin/x86_64-gcc75_glibc228-linux-gnu-ld -v
GNU ld (crosstool-NG 1.24.0.500_645889f) 2.27
$ /f/tc/x86_64-gcc75_glibc228-linux-gnu/bin/x86_64-gcc75_glibc228-linux-gnu-as repro.s
repro.s: Assembler messages:
repro.s:2: Error: found 'L', expected: ')'
repro.s:2: Error: junk at end of line, first unrecognized character is `L'
This other one relying on 2.26 fails both on 1U and 1UL:
$ ld -v
GNU ld version 2.26.20160125
$ as repro.s
repro.s: Assembler messages:
repro.s:1: Error: missing ')'
repro.s:1: Error: junk at end of line, first unrecognized character is `U'
repro.s:2: Error: missing ')'
repro.s:2: Error: junk at end of line, first unrecognized character is `U'
And this one based on 2.29 works for both:
$ /dev/shm/gcc-5.5.0-nolibc/x86_64-linux/bin/x86_64-linux-ld -v
GNU ld (GNU Binutils) 2.29.1.20170915
$ /dev/shm/gcc-5.5.0-nolibc/x86_64-linux/bin/x86_64-linux-as repro.s
So it just means that the support for the "U" suffix on numbers was
added in binutils 2.27 and the "L" suffix on numbers was added somewhere
between 2.27 and 2.29.
And given that there's a single occurrence of all this in the whole tree,
that's why I'm proposing to just get back to the good old (1 << 0) instead
of BIT(0).
Thanks!
Willy
next prev parent reply other threads:[~2023-04-16 8:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 3:12 [BUG REPORT] arch/x86/include/asm/uaccess_64.h:119: Error: junk at end of line Jingbo Xu
2023-03-14 10:23 ` Borislav Petkov
2023-03-14 11:04 ` Jingbo Xu
2023-04-15 17:56 ` Willy Tarreau
2023-04-15 18:56 ` Borislav Petkov
2023-04-16 8:36 ` Willy Tarreau [this message]
2023-04-17 18:14 ` Borislav Petkov
2023-04-17 18:32 ` H. Peter Anvin
2023-04-17 19:26 ` Borislav Petkov
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=ZDuzlNOmIT0Gd7fF@1wt.eu \
--to=w@1wt.eu \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jefflexu@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.