headers
Steven Bosscher | 1 Jun 2003 01:07
Picon
Picon

Re: [tree-ssa] Integrating g95

Diego Novillo wrote:

>Hmm, I'm not sure about this.  If we are going to move it, I think it
>might be best to make the switch at once.  Why do you think it would be
>more convenient to keep the two repositories?
>
>  
>
Because we have more people with write access to our SourceForge 
repository than we have people with GCC write access.  In fact, even 
Paul does not have GCC CVS write (hint), only Toon and I do.

Gr.
Steven
Permalink | Reply | 1 comment |
headers
Steven Bosscher | 1 Jun 2003 01:19
Picon
Picon

Re: [tree-ssa] Integrating g95

OK, so here is a check list of what we need to do before we can pass 
that tarball to Diego (following the page Joseph pointed to):

    * A directory language under gcc containing source files for that 
front end. See The Front End language Directory, for details.

Check!!!

    * A mention of the language in the list of supported languages in 
gcc/doc/install.texi.

TODO

    * Details of contributors to that front end in gcc/doc/contrib.texi. 
If the details are in that front end's own manual then there should be a 
link to that manual's list in contrib.texi.

Just the link to our own docs will suffice?

    * Information about support for that language in gcc/doc/frontends.texi.

TODO -- probably with a hint that it is not complete yet.

    * Information about standards for that language, and the front end's 
support for them, in gcc/doc/standards.texi. This may be a link to such 
information in the front end's own manual.

TODO -- I think this again will just be a link to the g95 manual to-be.

    * Details of source file suffixes for that language and -x lang
(Continue reading)

Permalink | Reply | 18 comments |
headers
Joseph S. Myers | 1 Jun 2003 01:32
Picon
Picon
Favicon

Re: [tree-ssa] Integrating g95

On Sun, 1 Jun 2003, Steven Bosscher wrote:

(The entries below here are in the second list in sourcebuild.texi - for
those integrated into GCC CVS, which really means mainline GCC CVS.  So
some of them aren't appropriate to do yet, though some can still be done
on the branch.)

>     * At least one GNATS category for bugs in that front end and runtime 
> libraries. This category needs to be mentioned in gcc/gccbug.in, and in 
> gnats.html on the GCC web site, as well as being added to the GNATS 
> database.
> 
> TODO -- what would be the appropriate name?  We should avoid confusion 
> so that our bugs don't end up in the category for g77.

Only relevant at this point if you want tree-ssa bug reports against G95
to go into GCC Bugzilla.

>     * Normally, one or more maintainers of that front end listed in 
> MAINTAINERS.
> 
> Paul, Toon and myself (when I finally contribute some patch again myself 
> :))?

This could always be done on the mainline MAINTAINERS - no need to branch
that file.

>     * Mentions on the GCC web site in index.html and frontends.html, 
> with any relevant links on readings.html. (Front ends that are not an 
> official part of GCC may also be listed on frontends.html, with relevant
(Continue reading)

Permalink | Reply | 1 comment |
headers
Neil Booth | 1 Jun 2003 01:41
Picon

Re: Documenting tools necessary for GCC [draft]

Toon Moene wrote:-

> Joseph S. Myers wrote:
> 
> >Will there be sound recordings (ogg or mp3) made available of the
> >discussions leading to specific policy decisions (e.g., to mandate GNU
> >make), together with transcripts of at least the actual decisions?
> 
> Duh !  I hope no-one gets from the messages about this subject that some 
> sort of decision was made at the GCC Summit.

That would be my fault.  IIRC re gmake it was agreed amongst ourselves
that gmake would be a good idea, but Alexandre suggested we should ask
Nathanael and I think DJ and maybe someone else too.

Neil.
Permalink | Reply | 0 comments |
headers
Steven Bosscher | 1 Jun 2003 02:08
Picon
Picon

Re: [tree-ssa] Integrating g95

Joseph S. Myers wrote:

>On Sun, 1 Jun 2003, Steven Bosscher wrote:
>  
>
>>    * At least one GNATS category for bugs in that front end and runtime 
>>libraries. This category needs to be mentioned in gcc/gccbug.in, and in 
>>gnats.html on the GCC web site, as well as being added to the GNATS 
>>database.
>>
>>TODO -- what would be the appropriate name?  We should avoid confusion 
>>so that our bugs don't end up in the category for g77.
>>    
>>
>
>Only relevant at this point if you want tree-ssa bug reports against G95
>to go into GCC Bugzilla.
>

I'm not sure.  It's not like we're in bug fix mode yet, more like 
complete-features-mode, so we should probably not clutter the gcc-bugs 
mainling list and database.  I removed this point from the list.

>>    * Normally, one or more maintainers of that front end listed in 
>>MAINTAINERS.
>>
>>Paul, Toon and myself (when I finally contribute some patch again myself 
>>:))?
>>    
>>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Steven G. Kargl | 1 Jun 2003 02:41
Picon

Re: [G95] Re: [tree-ssa] Integrating g95

Steven Bosscher wrote:

>
> TODO -- but we do not have much of a manual yet.  I was actually kinda
> hoping Steven Kargl and maybe Katherine would like to help with that
> (hint :)), being native speakers with American spelling.  I plan to work
> on this as long as I'm unable to build gcc's on my "new" computer.
>
I can help edit and write parts of a manual, but I have very
limited time so being the primary manual writer is not an
option.  I also have zero experience with texinfo.

There is one other item to consider.  g95 requires GMP.
AFAIK, GCC does not use GMP.  What are the options?

--

-- 
steve
Permalink | Reply | 15 comments |
headers
law | 1 Jun 2003 02:47
Picon
Favicon

Re: [tree-ssa] Integrating g95

In message <3ED935B7.9000003 <at> student.tudelft.nl>, Steven Bosscher writes:
 >Diego Novillo wrote:
 >
 >>Hmm, I'm not sure about this.  If we are going to move it, I think it
 >>might be best to make the switch at once.  Why do you think it would be
 >>more convenient to keep the two repositories?
 >>
 >>  
 >>
 >Because we have more people with write access to our SourceForge 
 >repository than we have people with GCC write access.  In fact, even 
 >Paul does not have GCC CVS write (hint), only Toon and I do.
That's a problem that can be easily resolved.

jeff
Permalink | Reply | 0 comments |
headers
law | 1 Jun 2003 02:48
Picon
Favicon

Re: [tree-ssa] Integrating g95

In message <1054421594.21692.437.camel <at> frodo.toronto.redhat.com>, Diego Novillo
 writes:
 >Hmm, I'm not sure about this.  If we are going to move it, I think it
 >might be best to make the switch at once.  Why do you think it would be
 >more convenient to keep the two repositories?
I'd strongly favor only having the code in one repository.  

jeff
Permalink | Reply | 0 comments |
headers
Wolfgang Bangerth | 1 Jun 2003 03:36
Picon

RESOLVED states in bugzilla


Bugzilla presently offers lots of resolutions for RESOLVED PRs. These I 
think are useful:
    Fixed
    Invalid
    Duplicate
These are doubtful. I haven't seen a PR where someone said "We're never 
going to fix this", but it won't hurt to have this; and WORKSFORME is not 
a very strong statement:
    Wontfix
    Worksforme

These I think are not useful:
    Remind
    Later
If a bug is not fixed now, it should remain open, not be closed and have a 
special state. Dan, can you say who invented these states and why? I don't 
see any use for them, and by the rule of maximal simplicity, would like to 
get rid of them if possible.

W.

-------------------------------------------------------------------------
Wolfgang Bangerth              email:            bangerth <at> ices.utexas.edu
                               www: http://www.ices.utexas.edu/~bangerth/
Permalink | Reply | 8 comments |
headers
law | 1 Jun 2003 04:01
Picon
Favicon

Re: [tree-ssa] Insert on edge comment

In message <Pine.LNX.4.44.0305311132300.22731-100000 <at> nondot.org>, Chris Lattner
 writes:
 >IMO, the real problem in tree-ssa is that it uses a nested control flow
 >structure instead of a linearized one...
Amen.  It's a model I'd like to move away from, it introduces a fair
amount of complexity.  However, it's pretty far down on the list of
things to do right now, but it's definitely on my list.

Jeff
Permalink | Reply | 6 comments |

Gmane