From: David Malcolm <dmalcolm@redhat.com>
To: RICHU NORMAN <richunorman@cusat.ac.in>
Cc: gcc@gcc.gnu.org
Subject: Re: Adding log files to gcc dump and adding testcase-rtl
Date: Wed, 25 May 2022 08:39:01 -0400 [thread overview]
Message-ID: <584fb8cfee848558abab42d799931ab262ae56d6.camel@redhat.com> (raw)
In-Reply-To: <CAPhpueXDV-31PZ53zk6A3utiKqqftYAveCoeK=ossMWKimHD7g@mail.gmail.com>
On Wed, 2022-05-25 at 16:32 +0530, RICHU NORMAN wrote:
> This is great, thank you so much!
You're welcome.
> I am also looking for support regarding adding instructions for the
> target
> machine.
That's something I've not done (my expertise is mostly in the frontends
and diagnostics).
With that caveat, I believe the official documentation is here:
https://gcc.gnu.org/onlinedocs/gccint/Machine-Desc.html
FWIW one of my colleagues wrote a series of posts about how to add an
entirely new CPU to the GNU toolchain here (originally called "ggx",
but now "moxie"):
http://atgreen.github.io/ggx/
though that's from 2008 so might be out-of-date, and covers the whole
toolchain, not just GCC, so might be overwhelming.
Hope this is helpful
Dave
>
>
>
> On Wed, May 25, 2022 at 4:14 PM David Malcolm <dmalcolm@redhat.com>
> wrote:
>
> > On Wed, 2022-05-25 at 10:25 +0530, RICHU NORMAN wrote:
> > > Hi,
> > > I am a beginner in gcc. I am trying to add an instruction to riscv-
> > > gcc.It
> > > would be helpful could help with a few tips .
> >
> > Hi Richu - welcome to GCC development.
> >
> > FWIW I've written a guide for new GCC contributors which you might
> > find
> > helpful:
> > https://gcc-newbies-guide.readthedocs.io/en/latest/index.html
> >
> > Caveat: I'm much more familiar with the frontends/diagnostics, rather
> > than the backends/RTL, so there may be a "frontend" bias in that
> > guide.
> >
> > > 1.How to write comments to rtl or create a custom log file to log
> > > comments
> > > to rtl dump?
> > > 2.How to run testsuite ?
> > > 3.Is there a way to directly run an rtl test case? Like giving rtl
> > > input
> > > and checking the generated asm.(Like in the attachment which is
> > > posted in
> > > bugzilla[ https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82815 ])
> > > Please suggest a way to run the gcc-testsuite with these cases. Pfa
> >
> > I wrote some notes on dealing with the testsuite, and on running
> > individual cases here:
> >
> >
> > https://gcc-newbies-guide.readthedocs.io/en/latest/working-with-the-testsuite.html
> >
> > Hope this is helpful; good luck
> > Dave
> >
> >
>
prev parent reply other threads:[~2022-05-25 12:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 4:55 RICHU NORMAN
2022-05-25 10:44 ` David Malcolm
2022-05-25 10:54 ` David Malcolm
2022-05-25 11:02 ` RICHU NORMAN
2022-05-25 12:39 ` David Malcolm [this message]
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=584fb8cfee848558abab42d799931ab262ae56d6.camel@redhat.com \
--to=dmalcolm@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=richunorman@cusat.ac.in \
/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).