From: Ian Lance Taylor <iant@google.com>
To: Nathan Froyd <froydnj@codesourcery.com>
Cc: "Diego Novillo" <dnovillo@google.com>,
"Manuel López-Ibáñez" <lopezibanez@gmail.com>,
"Steven Bosscher" <stevenb.gcc@gmail.com>,
"Grigori Fursin" <gfursin@gmail.com>,
"Dorit Nuzman" <DORIT@il.ibm.com>,
gcc@gcc.gnu.org
Subject: Re: Notes from the GROW'10 workshop panel (GCC research opportunities workshop)
Date: Wed, 14 Apr 2010 19:42:00 -0000 [thread overview]
Message-ID: <mcrd3y1suyi.fsf@dhcp-172-17-9-151.mtv.corp.google.com> (raw)
In-Reply-To: <20100414154431.GR540@codesourcery.com> (Nathan Froyd's message of "Wed\, 14 Apr 2010 08\:44\:32 -0700")
Nathan Froyd <froydnj@codesourcery.com> writes:
> On Wed, Apr 14, 2010 at 11:30:44AM -0400, Diego Novillo wrote:
>
>> To attract new developers, GCC needs to modernize its internal
>> structure. I have some thoughts on that, but progress has been slow,
>> due mostly to resource constraints.
>
> Would you mind expanding--even just a little bit--on what bits need
> modernizing?
The tree/GIMPLE layer needs significantly better documentation, but is
otherwise not too bad.
Once you get to the RTL layer, there are too many undocumented
inter-pass dependencies.
The interface between the frontend and the middle-end is largely
undocumented.
Ian
next prev parent reply other threads:[~2010-04-14 19:19 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-11 14:01 Dorit Nuzman
2010-04-11 18:27 ` Chris Lattner
2010-04-11 19:38 ` Grigori Fursin
2010-04-11 20:25 ` Chris Lattner
2010-04-11 20:58 ` Grigori Fursin
2010-04-14 14:34 ` Grigori Fursin
2010-04-14 14:58 ` Steven Bosscher
2010-04-14 15:21 ` Manuel López-Ibáñez
2010-04-14 15:30 ` Steven Bosscher
2010-04-14 15:36 ` Diego Novillo
2010-04-14 15:50 ` Nathan Froyd
2010-04-14 15:57 ` Richard Guenther
2010-04-14 19:19 ` Tom Tromey
2010-04-14 16:06 ` Diego Novillo
2010-04-14 18:30 ` Richard Guenther
2010-04-14 18:49 ` Toon Moene
2010-04-14 19:52 ` Basile Starynkevitch
2010-04-14 20:31 ` Toon Moene
2010-04-14 20:43 ` Toon Moene
2010-04-14 21:02 ` Ian Lance Taylor
2010-04-14 21:34 ` Manuel López-Ibáñez
2010-04-15 8:26 ` Basile Starynkevitch
2010-04-15 8:38 ` Manuel López-Ibáñez
2010-04-15 12:03 ` Basile Starynkevitch
2010-04-15 12:07 ` Andrew Haley
2010-04-15 12:15 ` Steven Bosscher
2010-04-15 12:17 ` Andrew Haley
2010-04-22 9:18 ` Laurent GUERBY
2010-04-14 21:04 ` Nathan Froyd
2010-04-14 19:42 ` Ian Lance Taylor [this message]
2010-04-14 15:44 ` Duncan Sands
2010-04-15 9:05 ` Manuel López-Ibáñez
2010-04-16 12:36 ` Grigori Fursin
2010-04-16 17:15 ` Manuel López-Ibáñez
2010-04-16 17:40 ` Grigori Fursin
2010-04-27 12:40 ` Grigori Fursin
2010-04-27 16:31 ` Manuel López-Ibáñez
2010-04-27 18:42 ` Grigori Fursin
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=mcrd3y1suyi.fsf@dhcp-172-17-9-151.mtv.corp.google.com \
--to=iant@google.com \
--cc=DORIT@il.ibm.com \
--cc=dnovillo@google.com \
--cc=froydnj@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=gfursin@gmail.com \
--cc=lopezibanez@gmail.com \
--cc=stevenb.gcc@gmail.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).