From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id A0EED385841D; Wed, 24 May 2023 09:58:59 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A0EED385841D DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1684922339; bh=aa4EJUMsCcOhoaTjRnRDPFbG9sNzdMVKJVPzJzUHpXE=; h=From:To:Subject:Date:In-Reply-To:References:From; b=WDM3pHBU2N/O/2j6eCviRiXtq+WHw+THbeNsGNWjTm9oSG7pRqWI7oPpIWUqmO02H iYg0wfhUcF947nVhGryKVNGyrqggmBT2N7FcRJ7S1BbXSK/K6NYSxG35dVrir+4OCF FYCMb823EaUhG1qJ9fnZWYCp/O7BpTAetpuSzF/E= From: "jbeulich at suse dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/109954] x86-64's -m32 does not conform to documentation Date: Wed, 24 May 2023 09:58:58 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 13.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jbeulich at suse dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- 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=3D109954 --- Comment #3 from jbeulich at suse dot com --- (In reply to Jakub Jelinek from comment #2) > So s/on any i386 system/in 32-bit mode/ ? Not sure. So far I was under the (possibly wrong) impression that -m32 would produce objects sufficiently similar to those a 32-bit compiler would produ= ce. After all environments like the Linux kernel use it with exactly that goal (aiui), albeit in combination with -march=3D. So if really it is documentat= ion to be adjusted, I think this aspect wants emphasizing more.=