public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "kernel coder" <lhrkernelcoder@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: RTL explaination
Date: Wed, 07 Jun 2006 13:06:00 -0000	[thread overview]
Message-ID: <f69849430606070605o707533fflc30a83e5b7c2730c@mail.gmail.com> (raw)

hi,
I'm trying to understand the rtl genrated by gcc for mips processor.I
have read gcc internals by Richard Stallman but there  are still some
confusions in the rtl language.

Following is a snippet of code which i'm trying to understand.

(insn 9 6 10 (nil) (set (reg:SI 182)
        (mem/f:SI (symbol_ref:SI ("a")) [0 a+0 S4 A32])) -1 (nil)
    (nil))

In the above code following part is still unclear to me

[0 a+0 S4 A32])) -1 (nil)
    (nil))

Following is the c code for which above rtl is generated :

int a;
main()
{
a=a+1;
}


thanks,
shahzad

                 reply	other threads:[~2006-06-07 13:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=f69849430606070605o707533fflc30a83e5b7c2730c@mail.gmail.com \
    --to=lhrkernelcoder@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    /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).