From: Helge Deller <deller@gmx.de>
To: Randy Dunlap <rdunlap@infradead.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-kernel@vger.kernel.org,
Michael Ellerman <mpe@ellerman.id.au>
Cc: linux-parisc@vger.kernel.org
Subject: Re: Build regressions/improvements in v6.0-rc5
Date: Tue, 20 Sep 2022 23:07:46 +0200 [thread overview]
Message-ID: <812d649c-380b-8a7e-1584-891c7e643656@gmx.de> (raw)
In-Reply-To: <d54e7e26-7797-bedb-142a-2101a4e497de@infradead.org>
On 9/20/22 22:29, Randy Dunlap wrote:
>
>
> On 9/20/22 13:23, Helge Deller wrote:
>> On 9/12/22 11:22, Geert Uytterhoeven wrote:
>>> On Mon, 12 Sep 2022, Geert Uytterhoeven wrote:
>>>> JFYI, when comparing v6.0-rc5[1] to v6.0-rc4[3], the summaries are:
>>>> - build errors: +16/-1
>>>
>>> + /kisskb/src/arch/parisc/kernel/vdso32/restart_syscall.S: Error: .cfi_endproc without corresponding .cfi_startproc: => 32
>>> + /kisskb/src/arch/parisc/kernel/vdso32/restart_syscall.S: Error: bad or irreducible absolute expression: => 16
>>> + /kisskb/src/arch/parisc/kernel/vdso32/restart_syscall.S: Error: junk at end of line, first unrecognized character is `:': => 16
>>> + /kisskb/src/arch/parisc/kernel/vdso32/restart_syscall.S: Error: no such instruction: `be 0x100(%sr2,%r0)': => 29
>>> + /kisskb/src/arch/parisc/kernel/vdso32/restart_syscall.S: Error: no such instruction: `ldi 0,%r20': => 30
>>> + /kisskb/src/arch/parisc/kernel/vdso32/restart_syscall.S: Error: no such instruction: `ldw 0(%sp),%r31': => 26
>>> + /kisskb/src/arch/parisc/kernel/vdso32/sigtramp.S: Error: no such instruction: `ble 0x100(%sr2,%r0)': => 46, 51
>>> + /kisskb/src/arch/parisc/kernel/vdso32/sigtramp.S: Error: no such instruction: `ldi 0,%r25': => 44
>>> + /kisskb/src/arch/parisc/kernel/vdso32/sigtramp.S: Error: no such instruction: `ldi 1,%r25': => 49
>>> + /kisskb/src/arch/parisc/kernel/vdso32/sigtramp.S: Error: no such instruction: `ldi 173,%r20': => 45, 50
>>> + /kisskb/src/arch/parisc/kernel/vdso32/sigtramp.S: Error: unknown pseudo-op: `.callinfo': => 40
>>> + /kisskb/src/arch/parisc/kernel/vdso32/sigtramp.S: Error: unknown pseudo-op: `.entry': => 41
>>> + /kisskb/src/arch/parisc/kernel/vdso32/sigtramp.S: Error: unknown pseudo-op: `.exit': => 54
>>> + /kisskb/src/arch/parisc/kernel/vdso32/sigtramp.S: Error: unknown pseudo-op: `.proc': => 39
>>> + /kisskb/src/arch/parisc/kernel/vdso32/sigtramp.S: Error: unknown pseudo-op: `.procend': => 55
>>> + /kisskb/src/arch/parisc/kernel/vdso32/sigtramp.S: Error: unknown pseudo-op: `.stringz': => 76
>>>
>>> parisc-gcc8/generic-32bit_defconfig
>>>
>>>> [1] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/80e78fcce86de0288793a0ef0f6acf37656ee4cf/ (all 135 configs)
>>>> [3] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/7e18e42e4b280c85b76967a9106a13ca61c16179/ (all 135 configs)
>>
>> I see those errors on the kiss website, but I'm unable to reproduce them.
>> Downloaded that .config, used same compiler (from https://mirrors.edge.kernel.org/pub/tools/crosstool/files/bin/x86_64/8.5.0/)....
>> Not sure how to get this fixed.
>> If someone has an idea or can reproduce, please let me know.
>
> Hi,
> I can reproduce it using the (x86_64 hosted) crosstool gcc-12.1.0 from kernel.org that Arnd builds/provides.
> https://mirrors.edge.kernel.org/pub/tools/crosstool/
Ah....
Building with "make ARCH=parisc CROSS_COMPILE=/some/path/nolibc/hppa-linux/bin/hppa-linux-"
uses this CROSS_COMPILE prefix for compiling the .c files, but not for the .S files.
So, you will end up with the default hppa-linux-gcc installed on the system, not the one provided
by CROSS_COMPILE.
Helge
next prev parent reply other threads:[~2022-09-20 21:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-11 21:03 Linux 6.0-rc5 Linus Torvalds
2022-09-12 9:13 ` Build regressions/improvements in v6.0-rc5 Geert Uytterhoeven
2022-09-12 9:22 ` Geert Uytterhoeven
2022-09-20 20:23 ` Helge Deller
2022-09-20 20:29 ` Randy Dunlap
2022-09-20 21:07 ` Helge Deller [this message]
2022-09-21 18:29 ` Helge Deller
2022-09-23 11:52 ` Michael Ellerman
2022-09-12 11:59 ` Linux 6.0-rc5 Sudip Mukherjee
2022-09-12 14:01 ` Linus Torvalds
2022-09-12 16:44 ` Guenter Roeck
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=812d649c-380b-8a7e-1584-891c7e643656@gmx.de \
--to=deller@gmx.de \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--cc=rdunlap@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®