From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 5D780385828D; Thu, 4 Jan 2024 13:49:26 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5D780385828D DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1704376166; bh=mILZHkgIZmes40DhzghbvMCohwLFQRFE1nvTiP0+sdc=; h=From:To:Subject:Date:In-Reply-To:References:From; b=gE1kdVXwYhYqVC4lcMycoFImsulmyoIC/1ZcPxzuiSAzHm6jek7NXOCpDfPO9aqwM uaFfzOEteQT/OREkCqGDZZRQ7iFB+UjHIy4TVFEtysSOsnVlvKiDjPAjJGPecoa3n0 /WAERZ2AY+fl2O5RkMd4mnJYIjxy0k3KvajXg7T4= From: "hubicka at ucw dot cz" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/113233] LoongArch: target options from LTO objects not respected during linking Date: Thu, 04 Jan 2024 13:49:25 +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: 14.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: hubicka at ucw dot cz 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=3D113233 --- Comment #3 from Jan Hubicka --- > Confirm. But option save/restore has been always implemented: >=20 > .section .gnu.lto_.opts,"",@progbits > .ascii "'-fno-openmp' '-fno-openacc' '-fno-pie' '-fcf-protection" > .ascii "=3Dnone' '-mabi=3Dlp64d' '-march=3Dloongarch64' '-mfpu=3D64'= '-m" > .ascii "simd=3Dlasx' '-mcmodel=3Dnormal' '-mtune=3Dloongarch64' '-fl= to" > .ascii "'\000" >=20 > So -msimd=3Dlasx is correctly recorded. Not sure why it does not work. With LTO we need to mix code compiled with different sets of options. For this reason we imply for every function defition and optimization and target attribute which record the flags. So it seems target attribute is likely broken for this flag.=