public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/107025] New: gas doesn't accept code produced by -mcpu=thunderx3t110
Date: Sat, 24 Sep 2022 08:41:09 +0000	[thread overview]
Message-ID: <bug-107025-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 107025
           Summary: gas doesn't accept code produced by
                    -mcpu=thunderx3t110
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: rsandifo at gcc dot gnu.org
                CC: ktkachov at gcc dot gnu.org, pinskia at gcc dot gnu.org,
                    rearnsha at gcc dot gnu.org
  Target Milestone: ---
            Target: aarch64*-*-*

Compiling:

void foo (_Atomic int *ptr) { ptr[1] = 1; }

with -O2 -mcpu=thunderx3t110 produces:

Error: selected processor does not support `stlur w1,[x0,4]'

This is because thunderx3t110 is listed as an Armv8.3-A core,
but includes the Armv8.4-A RCPC extension:

AARCH64_CORE("thunderx3t110",  thunderx3t110,  thunderx3t110, V8_3A, 
AARCH64_F\
L_CRYPTO | AARCH64_FL_RCPC | AARCH64_FL_SM4 | AARCH64_FL_SHA3 |
AARCH64_FL_F16F\
ML | AARCH64_FL_RCPC8_4, thunderx3t110, 0x43, 0x0b8, 0x0a)

This extension doesn't have its own separate feature flag in
gcc, gas, or clang.  I guess the options are to add one or
to remove the AARCH64_FL_RCPC8_4 entry.

             reply	other threads:[~2022-09-24  8:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-24  8:41 rsandifo at gcc dot gnu.org [this message]
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
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@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).