public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.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	[thread overview]
Message-ID: <bug-107025-4-p0B3sc67XV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107025-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107025

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 (essentially
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

  parent reply	other threads:[~2022-09-26  9:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-24  8:41 [Bug target/107025] New: " rsandifo at gcc dot gnu.org
2022-09-24 13:57 ` [Bug target/107025] " pinskia at gcc dot gnu.org
2022-09-26  9:34 ` ktkachov at gcc dot gnu.org [this message]
2022-09-29 10:34 ` cvs-commit at gcc dot gnu.org
2022-09-30 10:35 ` rsandifo at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-107025-4-p0B3sc67XV@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).