From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 98223385703F; Fri, 2 Jun 2023 08:50:53 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 98223385703F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1685695853; bh=7YgaU+IQQrLUjFj9k6j6cFg1MXsVplzKmula7y66BhY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=BwMCdCw5wZfpDuwmBcVd7FASRQ6sClN6g9buhdcuYBA7JZVkjnOWdPDQl6YMsvsVp KPJo/TOuEWeqWYp486A8aDmLmOdRjRThwOuO7kUL4CdrEyVlkD31s10uC1zw/3Knx2 gNI99GV2IXJzInueTAP5HNS/aeEIyaerPpq2HUYI= From: "arsen at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/109954] x86-64's -m32 does not conform to documentation Date: Fri, 02 Jun 2023 08:50:53 +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: documentation, patch X-Bugzilla-Severity: normal X-Bugzilla-Who: arsen at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 10.5 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 #20 from Arsen Arsenovi=C4=87 --- I agree, it's probably better to just update all references to be clear that -m32 generates IA32 code, rather than i?86 code. IMO, for multilib, it's reasonable to target the same CPU as -m64 in terms = of available extensions (as applicable), but in a different mode.=