Confusion in setting default options for non-C/C++ languages

2011-01-30 Thread Ian Lance Taylor
Currently toplev_main calls init_options_once init_options_struct lang_hooks.init_options_struct which all make sense. It then calls decode_options which calls default_options_optimization which sets various options based on the optimization level. That is fine provided all languages ag

Re: GCC 4.3.5 Status Report (2010-05-22)

2011-01-30 Thread Dongsheng Song
Oh, update_version_svn can be apply to trunk/gcc-4.5-branch/gcc-4.4-branch/gcc-4.3-branch, not only trunk. On Mon, Jan 31, 2011 at 10:45, Dongsheng Song wrote: > It's very simple (only for trunk, although it maybe more useful for branches): > > Index: update_version_svn >

Re: GCC 4.3.5 Status Report (2010-05-22)

2011-01-30 Thread Dongsheng Song
It's very simple (only for trunk, although it maybe more useful for branches): Index: update_version_svn === --- update_version_svn (revision 169428) +++ update_version_svn (working copy) @@ -42,6 +42,12 @@ SVNROOT2=${SVNROOT}/

Re: HEADS UP: [wwwdocs] Fix description of maintainer/reviewer privileges

2011-01-30 Thread Jonathan Wakely
On 31 January 2011 01:02, Gerald Pfeifer wrote: > >   Write after approval. >   This is folks that make regular contributions, but do not > -  fall into one of the two previous categories.  People with write > +  fall into one of the previous categories.  People with write >   after approval need t

Re: Heads up: please help documenting *internal* GCC changes for 4.6

2011-01-30 Thread Gerald Pfeifer
On Fri, 28 Jan 2011, Basile Starynkevitch wrote: > I am not sure to understand the technical ways to modify that; is CVS > still mandatory? Yes, the web pages reside in CVS. Not a lot different from SVN in terms of operations, just `cvs update`, `cvs diff`, `cvs commit` instead of the same svn co

HEADS UP: [wwwdocs] Fix description of maintainer/reviewer privileges

2011-01-30 Thread Gerald Pfeifer
I realized that our documentation has not been adjusted to (not so) recent changes and clarifications around the concepts of maintainers and reviewers we use. In fact, we don't have global maintainers any more and introduced the concept of reviewers. On the way I also tried to clarify that docume

Re: NetBSD bootstrap (was: Target deprecations for 4.6)

2011-01-30 Thread Jonathan Wakely
On 31 January 2011 00:25, Arnaud Lacombe wrote: > Hi, > > On Sat, Jan 29, 2011 at 5:24 PM, Jonathan Wakely > wrote: >> Ah, I did look in the NetBSD cvs repository and the other arches I >> looked at just used _ANSI_H_, I obviously didn't check the ones you >> identified. >> > From a quick look, d

Lilika Namzilma dod padomu Tev nevis trakot, bet

2011-01-30 Thread Gunnars
Nocheko so majaslapu un saac pelnit naudu jau tagad pec pamacibas luukojies sheit: http://www.negaiss-ir-prom.info Dailonis un Volmars jau pelna!

Re: NetBSD bootstrap (was: Target deprecations for 4.6)

2011-01-30 Thread Arnaud Lacombe
Hi, On Sat, Jan 29, 2011 at 5:24 PM, Jonathan Wakely wrote: > Ah, I did look in the NetBSD cvs repository and the other arches I > looked at just used _ANSI_H_, I obviously didn't check the ones you > identified. > >From a quick look, dreamcast, landisk, hpcsh, usermode and evbsh3 use fancy heade

Re: Making gcc -no-canonical-prefixes the default?

2011-01-30 Thread Gerald Pfeifer
On Fri, 28 Jan 2011, Ian Lance Taylor wrote: > Some archealogy turned up this as the reason canonicalization was > inserted: > > http://gcc.gnu.org/ml/gcc/2003-02/msg01121.html > http://gcc.gnu.org/ml/gcc-patches/2003-02/msg01697.html > > Also relevant here is http://gcc.gnu.org/PR29931 . I am q

Re: Target deprecations for 4.6

2011-01-30 Thread Joseph S. Myers
On Mon, 31 Jan 2011, Gerald Pfeifer wrote: > On Fri, 28 Jan 2011, Joseph S. Myers wrote: > > Here is a concrete list I propose for deprecation in 4.6; please send > > any other suggestions, or say if you wish to volunteer to maintain one > > of these targets to avoid deprecation > > Thanks for

Re: Target deprecations for 4.6

2011-01-30 Thread Gerald Pfeifer
On Fri, 28 Jan 2011, Joseph S. Myers wrote: > Here is a concrete list I propose for deprecation in 4.6; please send > any other suggestions, or say if you wish to volunteer to maintain one > of these targets to avoid deprecation Thanks for doing this, Joseph! I am not sure how to formally handl

Re: GCC 4.3.5 Status Report (2010-05-22)

2011-01-30 Thread Gerald Pfeifer
On Sat, 29 Jan 2011, Dongsheng Song wrote: > Just for curiousness, why we bump the DATESTAMP when the last commit > is DATESTAMP changes on the branch ? As far as I am concerned, that's a bug (or a missing feature). The script in question is maintainer-scripts/update_version_svn in the GCC source

gcc-4.3-20110130 is now available

2011-01-30 Thread gccadmin
Snapshot gcc-4.3-20110130 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/4.3-20110130/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 4.3 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches

Re: GCC 4.3.5 Status Report (2010-05-22)

2011-01-30 Thread Joseph S. Myers
On Sun, 30 Jan 2011, Richard Guenther wrote: > On Sat, Jan 29, 2011 at 5:51 AM, Dongsheng Song > wrote: > > On Mon, May 24, 2010 at 03:44, Richard Guenther > > wrote: > >> > >> It would be nice if the scripts could check whether only DATESTAMP > >> changes were done since the last snapshot ... >

Re: GCC 4.3.5 Status Report (2010-05-22)

2011-01-30 Thread H.J. Lu
On Sun, Jan 30, 2011 at 11:13 AM, Richard Guenther wrote: > On Sat, Jan 29, 2011 at 5:51 AM, Dongsheng Song > wrote: >> On Mon, May 24, 2010 at 03:44, Richard Guenther >> wrote: >>> >>> It would be nice if the scripts could check whether only DATESTAMP >>> changes were done since the last snapsh

Re: GCC 4.3.5 Status Report (2010-05-22)

2011-01-30 Thread Richard Guenther
On Sat, Jan 29, 2011 at 5:51 AM, Dongsheng Song wrote: > On Mon, May 24, 2010 at 03:44, Richard Guenther > wrote: >> >> It would be nice if the scripts could check whether only DATESTAMP >> changes were done since the last snapshot ... > > Just for curiousness, why we bump the DATESTAMP when the

GROW 2011: deadline extended to 7 February 2011

2011-01-30 Thread Erven Rohou
The submission deadline for the 3rd Workshop on GCC Opportunities has been extended until 7 February 2011. CALL FOR PAPERS 3rd Workshop on