Re: typos

On Wed, Jul 03, 2013 at 12:41:42AM +0200, Veres Lajos wrote: > Hi, > > I wrote a small misspell finder/fixer script and when I have a little > spare time I clean OS projects with it. > (https://github.com/vlajos/misspell_fixer) > I ran it on this repository: > svn://gcc.gnu.org/svn/gcc/trunk > Th

RE: [boost] lots of warning with gcc-4.8.1 + boost-1.54.0

> Lots of warnings like this: > > ./boost/bind/arg.hpp:37:22: warning: typedef ‘T_must_be_placeholder’ locally > defined but not used [-Wunused-local-typedefs] > > when building 1.54.0 with gcc-4.8.1 (fedora f19) This warning is new in GCC 4.8, and I have been seeing a ton of them not just in boos

Re: --with-native-system-header-dir= vs -isysroot

On Tue, Jul 02, 2013 at 08:35:53PM -0400, Jack Howarth wrote: > I am wondering if there are any alternatives to resorting to > --with-native-system-header-dir= for building FSF gcc > on darwin once the SDK is removed from the / and only resides in the buried > SDK directory. The FSF gcc boots

--with-native-system-header-dir= vs -isysroot

I am wondering if there are any alternatives to resorting to --with-native-system-header-dir= for building FSF gcc on darwin once the SDK is removed from the / and only resides in the buried SDK directory. The FSF gcc bootstrap fails in the absence of /usr/include in the fixincludes step unle

PR 50025 (uniform initialization of class member of reference type)

Hi, I'm just wondering, is there any chance of fixing PR 50025 [1] soon? It concerns uniform initialization of a class member of reference type. I have been using GCC to do C++11 development for a while now, and this one bug has been a bit of an eyesore IMO, that has been keeping the "uniform" ou

Re: Plan for removing global state from GCC's internals

On Tue, Jul 2, 2013 at 3:25 PM, Joseph S. Myers wrote: > On Mon, 1 Jul 2013, Aaron Gray wrote: > >> I started to do this starting with the C++ parser class'izing it but >> no one was interested. > > The C++ parser types such as cp_parser and cp_lexer already do a good job > of avoiding global stat

typos

Hi, I wrote a small misspell finder/fixer script and when I have a little spare time I clean OS projects with it. (https://github.com/vlajos/misspell_fixer) I ran it on this repository: svn://gcc.gnu.org/svn/gcc/trunk The patch is around 800kb. What is the best way to handle this modifications? I

Re: Git mirror: asan branch

Thomas Schwinge writes: > If I configure my local Git checkout of the GCC Git mirror to include all > branches, per , > then I get: > > fatal: refs/remotes/origin/asan tracks both refs/heads/asan and > refs/remotes/asan > > Is that a l

Re: Plan for removing global state from GCC's internals

On Mon, 1 Jul 2013, Aaron Gray wrote: > I started to do this starting with the C++ parser class'izing it but > no one was interested. The C++ parser types such as cp_parser and cp_lexer already do a good job of avoiding global state. I am not an expert on good C++ coding practices and don't kno

Re: Git mirror email address mangling

On 2013.07.02 at 19:53 +0200, Thomas Schwinge wrote: > Hi! > > On Sat, 13 Apr 2013 19:25:28 +0200, Markus Trippelsdorf > wrote: > > I've attached a gcc_authors file (gathered from various sources), that > > could be > > used as a start. > > > thomas = Thomas Schwinge > > As seen for example

Git mirror: asan branch

Hi! If I configure my local Git checkout of the GCC Git mirror to include all branches, per , then I get: fatal: refs/remotes/origin/asan tracks both refs/heads/asan and refs/remotes/asan Is that a local problem of mine, or a glitch i

Re: Git mirror email address mangling

Hi! On Sat, 13 Apr 2013 19:25:28 +0200, Markus Trippelsdorf wrote: > I've attached a gcc_authors file (gathered from various sources), that could > be > used as a start. > thomas = Thomas Schwinge As seen for example in commit e6f3cf6849f4e3169e0a520aaef772a13ea7a958, sourceware.org/gcc.gnu.

Re: Plan for removing global state from GCC's internals

Aaron: have you done the patch submission paperwork with the FSF? (as per http://gcc.gnu.org/contribute.html#legal ) If so, is your work available somewhere? Thanks Dave On Mon, 2013-07-01 at 23:56 +0100, Aaron Gray wrote: > I started to do this starting with the C++ parser class'izing it but >

Re: Plan for removing global state from GCC's internals

On Mon, 2013-07-01 at 19:43 +, Joseph S. Myers wrote: > On Mon, 1 Jul 2013, David Malcolm wrote: [...] > > Would you be in favor killing off these macros: > > #define input_line LOCATION_LINE (input_location) > > #define input_filename LOCATION_FILE (input_location) > > #define in_system_