Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: David Laight <david.laight.linux@gmail.com>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: Willy Tarreau <w@1wt.eu>, Shuah Khan <shuah@kernel.org>,
	"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
	Helge Deller <deller@gmx.de>,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	linux-parisc@vger.kernel.org
Subject: Re: [PATCH] tools/nolibc: add 64-bit parisc support
Date: Mon, 24 Aug 2026 09:19:58 +0100	[thread overview]
Message-ID: <20260824091958.7810094f@pumpkin> (raw)
In-Reply-To: <20260820-nolibc-parisc64-v1-1-067ebe7c8efb@weissschuh.net>

On Thu, 20 Aug 2026 11:32:50 +0200
Thomas Weißschuh <linux@weissschuh.net> wrote:

> Extend the existing parisc support to also handle 64-bit mode.
> 
> Some peculiarities:
> * The nonstandard ftruncate64 system call requires a workaround.
> * The linker defaults to main() as entry point, which needs to be
>   switched to _start() explicitly.
> * The linker defaults to dynamic linking, which needs to be disabled
>   explicitly.
> * With the default -Os, gcc does not use 64-bit multiplication
>   instructions, requiring libgcc. Use -O2 instead.
> * There is no qemu-user available.
> * CONFIG_COMPAT needs to be disabled to avoid build errors due to a
>   missing 32-bit vDSO compiler.
...
> diff --git a/tools/testing/selftests/nolibc/run-tests.sh b/tools/testing/selftests/nolibc/run-tests.sh
> index 3da806e2b302..a50a47d9df2c 100755
> --- a/tools/testing/selftests/nolibc/run-tests.sh
> +++ b/tools/testing/selftests/nolibc/run-tests.sh
> @@ -29,7 +29,7 @@ all_archs=(
>  	sparc32 sparc64
>  	m68k
>  	sh4
> -	parisc32
> +	parisc32 parisc64
>  	alpha
>  	hexagon
>  )
> @@ -122,6 +122,7 @@ crosstool_arch() {
>  	sparc*) echo sparc64;;
>  	x32*) echo x86_64;;
>  	parisc32) echo hppa;;
> +	parisc64) echo hppa64;;
>  	*) echo "$1";;
>  	esac
>  }
> @@ -206,11 +207,11 @@ test_arch() {
>  			exit 1
>  	esac
>  	printf '%-15s' "$arch:"
> -	if [ "$arch" = "m68k" -o "$arch" = "sh4" -o "$arch" = "openrisc" -o "$arch" = "parisc32" -o "$arch" = "alpha" ] && [ "$llvm" = "1" ]; then
> +	if [ "$arch" = "m68k" -o "$arch" = "sh4" -o "$arch" = "openrisc" -o "$arch" = "parisc*" -o "$arch" = "alpha" ] && [ "$llvm" = "1" ]; then

Would it be better to put the llvm condition first?

>  		echo "Unsupported configuration"

"Unsupported compiler" ?

>  		return
>  	fi
> -	if [ "$arch" = "x32" ] && [ "$test_mode" = "user" ]; then
> +	if [ "$arch" = "x32" -o "$arch" = "parisc64" ] && [ "$test_mode" = "user" ]; then

Ditto.

David

>  		echo "Unsupported configuration"
>  		return
>  	fi
> 
> ---
> base-commit: 7f4233794df172ab1d286dc0fbd70da2cc837654
> change-id: 20260407-nolibc-parisc64-3ca0547c2af9
> 
> Best regards,
> --  
> Thomas Weißschuh <linux@weissschuh.net>
> 
> 


      parent reply	other threads:[~2026-08-24  8:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-20  9:32 [PATCH] tools/nolibc: add 64-bit parisc support Thomas Weißschuh
2026-08-23 19:19 ` Rolf Eike Beer
2026-08-24  8:19 ` David Laight [this message]

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=20260824091958.7810094f@pumpkin \
    --to=david.laight.linux@gmail.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=deller@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=linux@weissschuh.net \
    --cc=shuah@kernel.org \
    --cc=w@1wt.eu \
    /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