From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id ACA483847700; Wed, 3 Apr 2024 08:00:19 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org ACA483847700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1712131219; bh=/1tzK7ZTIaf/ywEDhVp8437vl78j3gcucw4Hk8AVL1Y=; h=From:To:Subject:Date:In-Reply-To:References:From; b=TY3JZB8DbQr4CIL+tNvYhULDV852Unagkamm6i3CIpoLD2TY1FoMU5lS9XvOmzFw/ Jr+1THZ1uO/f5iqXDWNYytTlOqiuWwf+xzgSnsQmbdjGMwfkj2V6gkHxu1FEJYSEgM rKIzZhsIglY6mZ/ICl5G6uQ5ukpsJENDKckhEgWM= From: "mkuvyrkov at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/114568] [14 regression] g++.dg/vect/pr84556.cc fails to produce executable since r14-9706-gb8e7aaaf350a45 Date: Wed, 03 Apr 2024 08:00:19 +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: 14.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mkuvyrkov at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: mkuvyrkov at gcc dot gnu.org X-Bugzilla-Target-Milestone: 14.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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=3D114568 Maxim Kuvyrkov changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |clyon at gcc dot gnu.org, | |rearnsha at gcc dot gnu.org --- Comment #1 from Maxim Kuvyrkov --- The test now fails with linker error: .../arm-eabi/bin/ld: error: /tmp/cc2Q27GE.o: conflicting architecture profi= les A/M This is due to command line having -mthumb -march=3Darmv7-m -mtune=3Dcortex-m3 -mfloat-abi=3Dsoftfp -mfpu=3Dau= to ... -mfpu=3Dneon -mfloat-abi=3Dsoftfp -march=3Darmv7-a The first part comes from toolchain configuration settings, and the second = part (-mfpu=3Dneon -mfloat-abi=3Dsoftfp -march=3Darmv7-a) comes from check_effective_target_arm_neon_ok_nocache(). Surprisingly (to me), GCC accepts such mixed options, which makes check_effective_target_arm_neon_ok_nocache() succeed, since it's only doing= a compilation test. The linker, though, fails. Richard E., it is expected that GCC accepts conflicting -march=3D options?=