From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: weizhe wang <hmsjwzb@zoho.com>
Cc: gcc <gcc@gcc.gnu.org>
Subject: Re: seek advice about GCC learning
Date: Tue, 26 Sep 2023 07:40:51 +0100 [thread overview]
Message-ID: <CAH6eHdShqYitaZ0vvgGvhyFC=kJqPLpGzWEG5Nz2QZCUpvj07A@mail.gmail.com> (raw)
In-Reply-To: <18acf4045f5.fa6f7fea141941.7482616710276612130@zoho.com>
[-- Attachment #1: Type: text/plain, Size: 1900 bytes --]
On Tue, 26 Sept 2023, 03:11 weizhe wang via Gcc, <gcc@gcc.gnu.org> wrote:
> Hi Guys,
>
>
>
> Can we build risv-32 gcc compiler from official gcc repository ?
>
Yes, lots of people do that.
>
>
> Thanks,
>
>
>
> Flint
>
>
>
> Sent using https://www.zoho.com/mail/
>
>
>
>
>
>
>
>
> ---- On Thu, 02 Feb 2023 05:21:36 -0800 Martin Jambor <mjambor@suse.cz>
> wrote ---
>
>
>
> Hello Flint,
>
> On Sat, Jan 28 2023, hmsjwzb via Gcc wrote:
> > Hi GCC developers,
> >
> > I am learning GCC. But the GCC code is hard to understand.
>
> We are delighted you found looking into GCC interesting. I definitely
> agree that GCC source can be hard to read, especially for newcomers but
> often even for seasoned contributors when they look at a part they are
> not familiar with. But when you manage to manage to overcome the
> difficulty, the project can be very rewarding. And so not hesitate to
> ask us any specific question you may have here on the mailing list or on
> IRC.
>
> > I'm reading the c compiler of GCC. It seems the understanding of
> > AST/GENERIC representation is very important. Is there a tool
> > can visualize the AST/GENERIC representation?
>
> Intermediate representations like GENERIC, GIMPLE and RTL are indeed
> fundamental. In order to see the representation of instructions,
> compile a simple program with option -fdump-tree-all and examine the
> many files that will appear in your working directory (representation of
> things like aggregate data types is unfortunately somewhat missing).
>
> >
> > Do you have some advice for GCC beginner? Is there some
> documentations can help in the learning of GCC?
>
> David Malcolm wrote a very nice set of tutorials about various aspects
> of starting with GCC:
> https://gcc-newbies-guide.readthedocs.io/en/latest/
>
> I believe that is the best generic resource there is.
>
> Good luck,
>
> Martin
>
next prev parent reply other threads:[~2023-09-26 6:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-29 2:27 hmsjwzb
2023-02-02 13:21 ` Martin Jambor
2023-09-26 2:10 ` weizhe wang
2023-09-26 6:40 ` Jonathan Wakely [this message]
2023-09-26 6:48 ` weizhe wang
2023-09-27 17:12 ` David Brown
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='CAH6eHdShqYitaZ0vvgGvhyFC=kJqPLpGzWEG5Nz2QZCUpvj07A@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=hmsjwzb@zoho.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).