Re: Can GCC emit debug information to support debug uninitialized local variables

2010-06-19 Thread asmwarrior
On 2010-6-20 14:18, Ian Lance Taylor wrote: asmwarrior writes: My question is: Is there any possible that GCC can emit some debug information to indicate that one variable is initialed or not.(at least in the DEBUG build mode) You didn't mention which version of gcc you are testing.

Re: Can GCC emit debug information to support debug uninitialized local variables

2010-06-19 Thread Ian Lance Taylor
asmwarrior writes: > My question is: Is there any possible that GCC can emit some debug > information to indicate that one variable is initialed or not.(at > least in the DEBUG build mode) You didn't mention which version of gcc you are testing. With current gcc see if the -fvar-tracking option

gcc-4.6-20100619 is now available

2010-06-19 Thread gccadmin
Snapshot gcc-4.6-20100619 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/4.6-20100619/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 4.6 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/trunk

Re: GCC plugin support when using Ada

2010-06-19 Thread Duncan Sands
Hi PeteGarbett, I see nothing in the GCC 4.5 release notes about plugin support being language specific, and yet if I using the treehydra plugin with Ada (admittedly using a patched GCC 4.3.4 as per the dehydra notes), I get this I use plugins with Ada all the time, with gcc-4.5, and it works

Re: GCC plugin support when using Ada

2010-06-19 Thread Richard Guenther
On Fri, Jun 18, 2010 at 10:32 PM, PeteGarbett wrote: > > I see nothing in the GCC 4.5 release notes about > plugin support being language specific, and yet if I using the treehydra > plugin with Ada (admittedly using a patched GCC 4.3.4 as per the dehydra > notes), I get this > > gnat1: warning: c

ARM FLOOR_MOD_EXPR?

2010-06-19 Thread Jay K
Do FLOOR_DIV_EXPR and FLOOR_MOD_EXPR work on ARM, for 64bit signed integer? I have a front end (sort of), using gcc 4.3, generates trees, doesn't work.    type_for_mode(TImode) is NULL and that is dereferenced. I realize TRUNC_* would be far more "normal", but I can't change that. I guess I'll jus

Re: Experimental Patchwork setup

2010-06-19 Thread Ryan Hill
On Wed, 09 Jun 2010 08:13:02 +0200 Paolo Bonzini wrote: > Another point about (1): I believe patchwork should *not* track most of > the branch patches, and the commit detection shouldn't care about > release branch commits, only trunk. This is because those are 99% of > the time for trunk too