From: squirvel voxbox <squirvel@gmail.com>
To: crossgcc@sourceware.org
Subject: Defining a Super Specific uArch
Date: Tue, 12 Jan 2021 17:45:13 -0500 [thread overview]
Message-ID: <CAMdB7Vb0XH4zqTpgdWdR6aCcEymCij5Dbi_dX6L-T3GHiBN2Hg@mail.gmail.com> (raw)
Hi All,
I asked a fairly similar question over on the irc channel, and didn't get a
response, so I'm trying here.
Let's say I'm attempting to target a super specific CPU, (in this case a
RK3328, which is a 64bit armv8-a+crypto cpu). What would be the proper way
to define the cpu?
I am currently defining:
target architecture: arm
suffix to the arch-part: v8-a+crypto (according to gcc, the dash is
required to define v8-a)
emit assembly for CPU: cortex-a53
other items are set based on the sample aarch64-rpi3 configuration
But ct-ng build fails due to:
"Invalid configuration `aarch64v8-a+crypto-RK3328-linux-gnu': more than
four components" (so more than 4 dashes according to the script source code)
or if I disable the vendor string (set to RK3328)
"Invalid configuration `aarch64v8-a+crypto-linux-gnu': machine
`aarch64v8-a+crypto' not recognized"
In theory I could just add all the specific uarch flags to CFLAGS/LDFLAGS
such as -march=, but that feels rather hacky especially since there is an
arch suffix field.
Is the hacky way the way I should be defining this cpu, or am I just
specifying this incorrectly? If the latter, what is the proper way to
specify a super specific uarch?
Thanks,
squirvel
next reply other threads:[~2021-01-12 22:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 22:45 squirvel voxbox [this message]
2021-01-13 0:04 ` Chris Packham
2021-01-13 4:41 ` squirvel voxbox
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=CAMdB7Vb0XH4zqTpgdWdR6aCcEymCij5Dbi_dX6L-T3GHiBN2Hg@mail.gmail.com \
--to=squirvel@gmail.com \
--cc=crossgcc@sourceware.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).