From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 0B2A9385828E; Mon,  5 Feb 2024 13:24:11 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0B2A9385828E
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1707139452;
	bh=LjXSPCeXpFLQasM45kawNsF6RQ+gLIww/wl9PwyugLE=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=mdJjQGABnZnBnVIPJ1UYzxk2sy87RRgKAJMKDCQsix6tUtLnNXNZn+A6wO5oSgjPs
	 Nq11aoFRj+UbqXpXPvgY1484bIt5NR5J2RH/ORiTY3YtHToV3dnwZVXxD6WIpyMbwJ
	 UIRHuuH/AQ/SkxHEynPJqagr9FuWEnHy+cGQEdQo=
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/106680] Test gcc.target/powerpc/bswap64-4.c fails on
 32-bit BE
Date: Mon, 05 Feb 2024 13:24:08 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: linkw at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: linkw at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 13.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-106680-4-bW8wRm2AZE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-106680-4@http.gcc.gnu.org/bugzilla/>
References: <bug-106680-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D106680

--- Comment #11 from Kewen Lin <linkw at gcc dot gnu.org> ---
(In reply to Sebastian Huber from comment #8)
> Yes, it seems that -mcpu=3De6500 -mno-powerpc64 yields the right code for=
 the
> attached test case (with or without the -m32).

The default is -m32 I guess? :)

>=20
> I am now a bit confused what the purpose of the -m32 and -m64 options is.

For -m32/-m64, the manual says:

Generate code for 32-bit or 64-bit environments of Darwin and SVR4 targets
(including GNU/Linux). The 32-bit environment sets int, long and pointer to=
 32
bits and generates code that runs on any PowerPC variant. The 64-bit
environment sets int to 32 bits and long and pointer to 64 bits, and genera=
tes
code for PowerPC64, as for -mpowerpc64.

But it's possible to interact with option powerpc64, like cpu e6500 which by
default supports powerpc64 and if applied OS is able to support the necessa=
ry
context switches, we want -mpowerpc64 kept and it's able to generate more
efficient code (leveraging insns guarded with powerpc64 flag).=