From: SathisKanna <kanna@msrvr.indofuji.soft.net>
To: Alexender Pitschiburgh <pitschib@yahoo.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Doubt in GCC
Date: Sun, 05 May 2002 22:09:00 -0000 [thread overview]
Message-ID: <02050610411200.01170@sathis> (raw)
In-Reply-To: <20020505073934.89700.qmail@web21507.mail.yahoo.com>
Hi,
Thanks for the reply.
But in "gcc/f/target.c " mentioned that it converts the lexical token into
machine depantant numerical form.
That means gcc converts the source into device dependant for the target
architecture immediatly after the lexical analysis only(i.e while converting
token into tree format).
Is it correct??
Regards
sathis
On Sunday 05 May 2002 01:09 pm, you wrote:
> > Hi ALL,
> > In Which level the machine specific formats are
>
> included in GCC?
>
> > Regards
>
> In RTL generation...
>
>
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Health - your guide to health and wellness
> http://health.yahoo.com
next prev parent reply other threads:[~2002-05-06 5:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-05 0:39 Alexender Pitschiburgh
2002-05-05 22:09 ` SathisKanna [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-04 1:58 SathisKanna
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=02050610411200.01170@sathis \
--to=kanna@msrvr.indofuji.soft.net \
--cc=gcc-help@gcc.gnu.org \
--cc=pitschib@yahoo.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).