public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jim Wilson <wilson@redhat.com>
To: "Avinash J.K. Shrivastava" <avi@cse.iitb.ac.in>
Cc: gcc@gnu.org, naveens@noida.hcltech.com
Subject: Re: query about Gcc-backend..
Date: Wed, 02 Oct 2002 14:46:00 -0000	[thread overview]
Message-ID: <xwufzvopmul.fsf@tonopah.toronto.redhat.com> (raw)
In-Reply-To: <Pine.HPX.4.21.0210022328090.19898-100000@everest.cse.iitb.ac.in>

>[1] what is the way [mechanism] the backend of gcc accepts and handles the
>    tree-representation....

Pass a tree to expand_expr, and it emits RTL into the current instruction
stream.  expand_expr is in expr.c.

>[2] how exactly is done "the tree-RTL conversion"...

The md file is required to have certain named patterns which implement the
minimal set of operations from which all other operations can be derived.

For each tree code, there is one or more RTL generation strategies.  The
strategies generally involve calling named patterns in the md file.  If
there is more than one RTL generation strategy, then we use info from the
backend to decide which strategy to use.  This can involve checking to see
which named patterns are defined by this target.  This can involve comparing
relative costs of operations to determine which strategy is cheaper.  Etc.

>[3] how can we understand the broad-view of the routine(s), in the
>    file(s).

There is some info in the internals documentation.  See for instance
        http://gcc.gnu.org/onlinedocs/gccint/Passes.html#Passes
For a better understanding, you just have to spend some time studying the
gcc sources.

Jim

      parent reply	other threads:[~2002-10-02 21:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-02 12:27 Avinash J.K. Shrivastava
2002-10-02 12:39 ` Avinash J.K. Shrivastava
2002-10-02 14:46 ` Jim Wilson [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=xwufzvopmul.fsf@tonopah.toronto.redhat.com \
    --to=wilson@redhat.com \
    --cc=avi@cse.iitb.ac.in \
    --cc=gcc@gnu.org \
    --cc=naveens@noida.hcltech.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).