From: Erik Leunissen <elns@xs4all.nl>
To: crossgcc@sourceware.org
Subject: Target configuration with ct-ng and configurability of the resulting toolchain (regarding target)
Date: Mon, 22 Jan 2018 14:17:00 -0000 [thread overview]
Message-ID: <3c23dba7-6eb0-5f11-57b1-b49b7577857d@xs4all.nl> (raw)
Hi,
Can someone please enlighten me about how the choices in ct-ng regarding
target options, affect the targets or architectures that the resulting
toolchain can generate code for?
Context: I'm in the process of making a toolchain that supports arm
architectures as generically as possible, while still being able to
generate code that is tuned for a specific cpu, by make choices that
deviate from the ct-ng configuration when invoking the compiler (using
options like -march -m32/64 -mtune, -mcpu, -mfpu). At the very least I'd
like to generate code specifically tuned/optimised for cortex-a53 and
cortex-a8.
Examples:
Suppose I configure the target as "arm", and specify "cortex-a53" for
"Emit assembly for CPU" (in the category "toolchain optimisations"). Can
I still use the resulting toolchain to generate code for cortex-a8 by
specifying "-march=cortex-a8" on the compiler command line?
Likewise:
Suppose I configure the toolchain for 64-Bitness. Can I still use the
resulting toolchain to generate code for 32-bit architectures by
specifying "-m32" on the command line? And how about the converse case?
Again, likewise:
Suppose I configure the toolchain for software floating point
("softfp"). Can I still use the resulting toolchain to generate code
using hardware fp by specifying "-mfpu=neon-vfpv3" on the command line?
Thanks in advance for any insights or pointers,
Erik Leunissen.
reply other threads:[~2018-01-22 14:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3c23dba7-6eb0-5f11-57b1-b49b7577857d@xs4all.nl \
--to=elns@xs4all.nl \
--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).