From: Michael Matz <matz@suse.de>
To: Richard Biener <richard.guenther@gmail.com>
Cc: Claudio Eterno <eterno.claudio@gmail.com>, gcc@gcc.gnu.org
Subject: Re: gcc tricore porting
Date: Mon, 19 Jun 2023 14:16:48 +0000 (UTC) [thread overview]
Message-ID: <alpine.LSU.2.20.2306191406060.13548@wotan.suse.de> (raw)
In-Reply-To: <CAFiYyc2hVBsVApj5s_Sw-UrrsQ=h0Wjdd7i0wJ1QhRh1+_zDaQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1525 bytes --]
Hello,
On Mon, 19 Jun 2023, Richard Biener via Gcc wrote:
> On Sun, Jun 18, 2023 at 12:00 PM Claudio Eterno via Gcc <gcc@gcc.gnu.org> 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...
>
> We welcome ports to new architectures. Quick googling doesn't find me
> something like an ISA specification though so it's difficult to assess the
> complexity of porting to that architecture.
https://en.wikipedia.org/wiki/Infineon_TriCore
https://www.infineon.com/dgdl/TC1_3_ArchOverview_1.pdf?fileId=db3a304312bae05f0112be86204c0111
CPU part looks like fairly regular 32bit RISC. DSP part seems quite
normal as well. There even was once a GCC port to Tricore, version 3.3
from HighTec (now part of Infineon itself), but not even the wayback
machine has the files for that anymore:
https://web.archive.org/web/20150205040416/http://www.hightec-rt.com:80/en/downloads/sources.html
Given the age of that port it's probably better to start from scratch
anyway :) (the current stuff from them/Infineon doesn't seem to be
GCC-based anymore?)
Ciao,
Michael.
next prev parent reply other threads:[~2023-06-19 14:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-18 9:58 Claudio Eterno
2023-06-19 8:19 ` Richard Biener
2023-06-19 14:16 ` Michael Matz [this message]
2023-06-19 14:44 ` Claudio Eterno
2023-06-19 15:18 ` Michael Matz
2023-06-19 15:36 Mikael Pettersson
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
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=alpine.LSU.2.20.2306191406060.13548@wotan.suse.de \
--to=matz@suse.de \
--cc=eterno.claudio@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=richard.guenther@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).