From: Nathan Sidwell <nathan@codesourcery.com>
To: Sonawane Sachin Vijayku <sachinvs@cse.iitb.ac.in>
Cc: gcc@gnu.org, gcc@gcc.gnu.org
Subject: Re: GCC help
Date: Thu, 09 Sep 2004 10:37:00 -0000 [thread overview]
Message-ID: <4140304A.4070807@codesourcery.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0409091517340.3920@mars.cse.iitb.ac.in>
Sonawane Sachin Vijayku wrote:
> Hello,
> I am Sachin, doing M.Tech(CSE) in IIT Bombay.
> My project deals with the internals of GCC.
> Could you please tell me about the Research paper on the following topic?
> Topic is "DFA based instruction Scheduling", which is being implemented
> in GCC.
> Thanks in advance.
the scheduler is generated by genautomata.c. look there for references.
nathan
--
Nathan Sidwell :: http://www.codesourcery.com :: CodeSourcery LLC
nathan@codesourcery.com :: http://www.planetfall.pwp.blueyonder.co.uk
WARNING: multiple messages have this Message-ID
From: Nathan Sidwell <nathan@codesourcery.com>
To: Sonawane Sachin Vijayku <sachinvs@cse.iitb.ac.in>
Cc: gcc@gnu.org, gcc@gcc.gnu.org
Subject: Re: GCC help
Date: Thu, 09 Sep 2004 10:40:00 -0000 [thread overview]
Message-ID: <4140304A.4070807@codesourcery.com> (raw)
Message-ID: <20040909104000.jNYLc8pwU7KcLQHcxSrIkTBkzX1MDinpGPXmYLg2Q_s@z> (raw)
In-Reply-To: <Pine.LNX.4.61.0409091517340.3920@mars.cse.iitb.ac.in>
Sonawane Sachin Vijayku wrote:
> Hello,
> I am Sachin, doing M.Tech(CSE) in IIT Bombay.
> My project deals with the internals of GCC.
> Could you please tell me about the Research paper on the following topic?
> Topic is "DFA based instruction Scheduling", which is being implemented
> in GCC.
> Thanks in advance.
the scheduler is generated by genautomata.c. look there for references.
nathan
--
Nathan Sidwell :: http://www.codesourcery.com :: CodeSourcery LLC
nathan@codesourcery.com :: http://www.planetfall.pwp.blueyonder.co.uk
next prev parent reply other threads:[~2004-09-09 10:28 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-09 9:53 Sonawane Sachin Vijayku
2004-09-09 10:08 ` Sonawane Sachin Vijayku
2004-09-09 10:25 ` Ranjit Mathew
2004-09-09 10:37 ` Nathan Sidwell [this message]
2004-09-09 10:40 ` Nathan Sidwell
-- strict thread matches above, loose matches on Subject: below --
2010-05-18 18:11 gcc help packet
2010-05-18 18:18 ` Joel Sherrill
2005-11-30 22:40 pati (sent by Nabble.com)
2005-11-30 23:04 ` Mike Stump
2005-03-29 17:54 Gcc help andre
2005-03-29 18:10 ` andre
2005-03-29 19:02 ` Eljay Love-Jensen
2005-03-29 19:15 ` Eljay Love-Jensen
2004-01-22 8:22 gcc help Andrew
2004-01-22 22:06 ` Jim Wilson
2003-12-03 17:48 GCC help George Ciobanu
2003-12-04 20:10 ` Jim Wilson
2002-10-25 16:21 gcc help MICHAEL GOODWIN
2002-02-19 5:32 GCC help aditya nishandar
2002-02-19 8:12 ` Philipp Thomas
[not found] <616BE6A276E3714788D2AC35C40CD18D29DB3D@whale.softwire.co.uk>
2001-12-18 23:44 ` gcc help Rupert Wood
2001-12-18 12:16 ashish kamble
2001-10-14 22:12 GCC help pradeep kumar mishra
2001-10-15 4:49 ` Erik Mouw
2000-07-21 14:42 Gcc Help Anjul Srivastava
2000-07-21 14:35 Koaps
2000-07-21 14:49 ` Alexandre Oliva
2000-06-13 14:09 GCC Help Amir Elaguizy
2000-06-13 14:15 ` llewelly
2000-06-13 14:16 ` Mo McKinlay
2000-06-13 14:37 ` Alexandre Oliva
1998-12-15 10:18 Eric Methot
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=4140304A.4070807@codesourcery.com \
--to=nathan@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=gcc@gnu.org \
--cc=sachinvs@cse.iitb.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).