From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 0D5713858C5F; Mon, 6 Mar 2023 11:06:33 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0D5713858C5F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1678100793; bh=+/g2lgnMahZiRdQ8G2ITP8sSlEeLNLkwzYBZAXi97Uk=; h=From:To:Subject:Date:In-Reply-To:References:From; b=QcOq9p61F/LqOkg+gZVfUigtC1apksVusjR+IX6qbKbS8KdqcCnW/MbBHlYZ+LmEP D2aezgHevyAznomXLvkwxrT/3ZMmwpAFaeKz6EegXRcNB2OYW2qJ5WmdfYtiTJxP0d XOGZsbVmW7d0l0r9X0rcQckzWntGrUcj6+LYRsU4= From: "bugreporter66 at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/109007] building for POWER8 leaks into POWER9 ISA with g++ 11.3 (cross-compiler on x86_64 host) Date: Mon, 06 Mar 2023 11:06:31 +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: 11.3.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: bugreporter66 at gmail dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID 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=3D109007 --- Comment #18 from bugreporter66 at gmail dot com --- I noticed that building on newer Linux distros often produces a binary that then cannot run on older ones even with the same CPU, it requires newer libraries at runtime (tried that with x86_64). That alone limits backward-compatibility among Linux releases, but forward-compatibility does work (I always build release binaries on the oldest distro available, then = it works everywhere). So, I might be willing to let go of the idea of building for the older targ= ets on the up-to-date LTS release, and as a workaround I should always emulate = on the latest available CPU to future-proof for the next transitions.=