From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id E543C3858D32; Mon, 26 Sep 2022 09:34:56 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E543C3858D32 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1664184896; bh=GTq5L6M7weuq/iCB0hlq8uB5njhPQLxEJMEdrb639VY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=oECclA4rOawsnGeYzG0L1VNJBF6Cnvqf+kr3c2gUpW6j6TLZSh8jtaSHGSYsJAkTi npFxwCZqjYUGfSIVXTRsxIQHdAxlrotT2F2+BnB7vsqJ87wjZFKWSZ5l9Cm8Snm6ck p8x+FsVTUybbTSNkS/YQsu41NWL0c77pOe6ad02Y= From: "ktkachov at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/107025] gas doesn't accept code produced by -mcpu=thunderx3t110 Date: Mon, 26 Sep 2022 09:34:56 +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: 12.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ktkachov at gcc dot gnu.org 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: cf_reconfirmed_on everconfirmed bug_status 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=3D107025 ktkachov at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2022-09-26 Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #2 from ktkachov at gcc dot gnu.org --- In the Arm architecture this is FEAT_LRCPC2. LLVM does have an MC (essentia= lly assembler-level) feature string for it called "rcpc-immo", so if we wanted = to support this I guess we'd want to be compatible. That said, it may be cleaner to just remove support for thunderx3t110 if we think it's the right time. Unfortunately we do still have some cases where our features aren't fine-grained enough and are tied to architecture levels that some CPUs don't claim to support: https://godbolt.org/z/axbnd4c5o=