From: Gary Oblock <gary@amperecomputing.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: Gary Oblock via Gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Anybody ever got an ARM Thumb-2 cross compiler to work?
Date: Thu, 16 Jun 2022 07:11:02 +0000 [thread overview]
Message-ID: <BYAPR01MB54648970BDB00E26881C6F43C6AC9@BYAPR01MB5464.prod.exchangelabs.com> (raw)
In-Reply-To: <CAH6eHdSTMcR+xbCfFabsNCga5XDAj_ULkitH-2meRdXBOmZU3g@mail.gmail.com>
Jonathan
By off the shelf, I mean not creating a new target description file. Something
which I'm not at all experienced in (optimizations are my thing so I'm an
amateur at creating a cross-compiler.)
I can't seem to figure out what the binutils or the gcc target is for Thumb-2.
If you know, please let me know. I suspect that is an obsolete target
that no longer exists for the latest binutils and GCC 12.
Thanks,
Gary
________________________________
From: Jonathan Wakely <jwakely.gcc@gmail.com>
Sent: Wednesday, June 15, 2022 11:31 PM
To: Gary Oblock <gary@amperecomputing.com>
Cc: Gary Oblock via Gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Anybody ever got an ARM Thumb-2 cross compiler to work?
[EXTERNAL EMAIL NOTICE: This email originated from an external sender. Please be mindful of safe email handling and proprietary information protection practices.]
On Thu, 16 Jun 2022, 00:18 Gary Oblock via Gcc-help, <gcc-help@gcc.gnu.org<mailto:gcc-help@gcc.gnu.org>> wrote:
The subject line says it all...
I'm beginning to think off the shelf gcc cross compilers are impossible
to create because of binutils.
Why?
What do you mean by "off the shelf"?
At other companies we for the most part
created custom assemblers, loaders and libraries from scratch
when we built a gcc cross compiler.
Why can't you just build a cross binutils too?
next prev parent reply other threads:[~2022-06-16 7:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 23:17 Gary Oblock
2022-06-16 6:31 ` Jonathan Wakely
2022-06-16 7:11 ` Gary Oblock [this message]
2022-06-16 7:45 ` Christophe Lyon
2022-06-16 21:06 ` Gary Oblock
2022-06-17 7:25 ` Christophe Lyon
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=BYAPR01MB54648970BDB00E26881C6F43C6AC9@BYAPR01MB5464.prod.exchangelabs.com \
--to=gary@amperecomputing.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
/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).