|
From: | Lars Segerlund |
Subject: | Re: [Gomp-discuss] sentinels |
Date: | Tue, 04 Feb 2003 11:30:59 +0100 |
User-agent: | Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.2.1) Gecko/20021226 Debian/1.2.1-9 |
Ok, the C frontend is fine with me, and then we should wait for Scott for more info.
The question is how do we go about our modifications ? this as relates to the code changed, shall we keep private copies of some files which we use for the compilation of a omp capable gcc ? What I was thinking was to have a set of the files we change and mangle the build system ? In this way all our code is non-invasive to the rest of gcc ?
I would prefer if we could keep all our code contained in our own directory, what is the opinion here ?
Finally, when do we start ? Thoughts ? Steven Bosscher wrote:
Op di 04-02-2003, om 09:43 schreef Lars Segerlund:
...[snip]...
I think the Fortran stuff can wait. G95 is nowhere near complete and like I told you in a private discussion, the g95 parser is basically a template matcher that is to brittle that I would rather not touch it for a while. So IMHO it would be best to start with the C front end. The sooner we can show off our Great Effort to the GCC community, the more support we're likely to get, so I think we should be in GCC CVS. Some sub-branch from the tree-ssa branch to 1) implement the OMP C pragmas and 2) Define the tree codes to go with that?
...[snip]...
Agree. We can make the middle end just ignore the extra information for now, that's always legal.
...[snip]...
Scott said he would have a look at the differences between Fortran on the one hand and C/C++ on the other. I suggest we wait for him to draw conclusions and then decide which directives to implement first. Greetz Steven
[Prev in Thread] | Current Thread | [Next in Thread] |