From: Mikael Pettersson <mikpelinux@gmail.com>
To: eterno.claudio@gmail.com
Cc: GCC Development <gcc@gcc.gnu.org>
Subject: Re: gcc tricore porting
Date: Mon, 19 Jun 2023 17:36:00 +0200 [thread overview]
Message-ID: <CAM43=SP6gztzWifbt3tsYWMK-eUmwrhMd+iW0kdLS_jAwp96Cg@mail.gmail.com> (raw)
(Note I'm reading the gcc mailing list via the Web archives, which
doesn't let me
create "proper" replies. Oh well.)
On Sun Jun 18 09:58:56 GMT 2023, <eterno.claudio@gmail.com> wrote:
> Hi, this is my first time with open source development. I worked in
> automotive for 22 years and we (generally) were using tricore series for
> these products. GCC doesn't compile on that platform. I left my work some
> days ago and so I'll have some spare time in the next few months. I would
> like to know how difficult it is to port the tricore platform on gcc and if
> during this process somebody can support me as tutor and... also if the gcc
> team is interested in this item...
https://github.com/volumit has a port of gcc + binutils + newlib + gdb
to Tricore,
and it's not _that_ ancient. I have no idea where it originates from
or how complete
it is, but I do know the gcc-4.9.4 based one builds with some tweaks.
I don't know anything more about it, I'm just a collector of cross-compilers for
obscure / lost / forgotten / abandoned targets.
/Mikael
next reply other threads:[~2023-06-19 15:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 15:36 Mikael Pettersson [this message]
2023-06-19 16:54 ` Joel Sherrill
[not found] ` <CA+moFQ-JQJr6nxM+ce=m04riTk+4CcfDLnVk+3GJdrBh54D=7w@mail.gmail.com>
[not found] ` <CAF9ehCXjVhZ8ycWi4w+Qx3rB6Rf9-bKSg9q_96mhkWZUxnWmig@mail.gmail.com>
[not found] ` <CA+moFQ_nV5XiB+k9pE6-WbaiUo6Br-XVNSDKsomYbnnghOd00Q@mail.gmail.com>
[not found] ` <CA+moFQ8ymEvPpo9qTmr+7Jp=5HXp-s6yYj0dwTOg+yfDqN0PGg@mail.gmail.com>
[not found] ` <CAF9ehCUhHHTXLTTwWqtbxF8wNDN5pj=LJJuxEUKG91aXK24E5Q@mail.gmail.com>
2023-07-03 14:45 ` Richard Earnshaw (lists)
2023-06-19 16:56 ` Alexander Monakov
-- strict thread matches above, loose matches on Subject: below --
2023-06-18 9:58 Claudio Eterno
2023-06-19 8:19 ` Richard Biener
2023-06-19 14:16 ` Michael Matz
2023-06-19 14:44 ` Claudio Eterno
2023-06-19 15:18 ` Michael Matz
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='CAM43=SP6gztzWifbt3tsYWMK-eUmwrhMd+iW0kdLS_jAwp96Cg@mail.gmail.com' \
--to=mikpelinux@gmail.com \
--cc=eterno.claudio@gmail.com \
--cc=gcc@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).