From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 8F47A3858CDA; Mon, 5 Feb 2024 13:01:40 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8F47A3858CDA DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1707138100; bh=LUXjBKT1Tfl1zyZydiD27wzxB/JHAnxZ5L7z0vGRt1M=; h=From:To:Subject:Date:In-Reply-To:References:From; b=ETuJdCShmP6zL/o139zHL9Lu7yynjTAdIS0pkR3/4b3V9Ewmkk4SP02bzjOSOGfyO u13aqffqvEhI09C/A9BvL2vOTAG0Li27+e6PH4md3PKGMRAYCsqXbnPI+rt/VrHsrD bH8GwQNQwvaloqwTzRB2/Q/XA0p72wZxG1UdSNWU= From: "sebastian.huber@embedded-brains.de" 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:01:40 +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: sebastian.huber@embedded-brains.de 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: In-Reply-To: References: 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: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D106680 --- Comment #8 from Sebastian Huber --- Yes, it seems that -mcpu=3De6500 -mno-powerpc64 yields the right code for t= he attached test case (with or without the -m32). I am now a bit confused what the purpose of the -m32 and -m64 options is.=