public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: RICHU NORMAN <richunorman@cusat.ac.in>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: How target.md file with target.c/.cc file invoke assembly instructions
Date: Tue, 10 May 2022 11:57:04 +0100	[thread overview]
Message-ID: <CAH6eHdRca25pLC7e75bjcVfwf0WEsnyySRbxgGgnEpBL6-d3DA@mail.gmail.com> (raw)
In-Reply-To: <CAPhpueUFzxJNLdA_6Rj18N4nZB27O_bvrfVaSB5OdyP7x6us0A@mail.gmail.com>

On Tue, 10 May 2022 at 11:51, RICHU NORMAN wrote:
>
> Hi,
> I am new in gcc development and I am focusing on cross-compilers.I have
> added a few instructions for the target machine and invoked it using asm()
> from c program.Now I want to add those instructions to gcc and define that
> instruction in target.md file.I have a few queries regarding the working of
> gcc.
> 1. Do *target.md* files along with* target.cc/.c <http://target.cc/.c> *files
> help to invoke assembly instructions automatically?
> 2.What is the input for this ?(.Gimple or .cfg files)
> 3.How does it work internally?
> 4.I have defined an instruction in target.md alone.But that does not
> work.How to make it work?
> 5.Which file to be examined in rtl-dump of object file for getting the
> input and output to this stage in gcc?

This is the wrong mailing list for questions about GCC development:

https://gcc.gnu.org/lists.html

  reply	other threads:[~2022-05-10 10:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-10 10:50 RICHU NORMAN
2022-05-10 10:57 ` Jonathan Wakely [this message]
2022-05-10 13:24   ` RICHU NORMAN

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=CAH6eHdRca25pLC7e75bjcVfwf0WEsnyySRbxgGgnEpBL6-d3DA@mail.gmail.com \
    --to=jwakely.gcc@gmail.com \
    --cc=gcc-help@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).