problems with -fdump-tree options (gcc 4.1.2)

2009-03-25 Thread Tony Zhang
Hi, I tried the following: gcc-fdump-tree-all example.c, and i got these files: example.c.t00.tu , example.c.t02.original , example.c.t03.gimple , example.c.t06.vcg , I have two questions: How can i get example.c.original rather than example.c.t02.original? What does the symbol "t0x" stand

Successfull build of gcc-4.4.0 [trunk revision 145008] on i686-pc-cygwin

2009-03-25 Thread Rainer Emrich
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Compiler version: 4.4.0 20090323 (experimental) [trunk revision 145008] (GCC) Platform: i686-pc-cygwin configure flags: --prefix=/opt/devel/gnu/gcc/gcc-4.4.0/i686-pc-cygwin - --with-gmp=/opt/devel/gnu/gcc/gcc-4.4.0/i686-pc-cygwin - --with-mpfr=/opt/dev

Re: Successfull build of gcc-4.4.0 [trunk revision 145008] on i686-pc-cygwin

2009-03-25 Thread Eric Botcazou
> For the acats tests most of the FAIL cases ar of the form: > violation of restriction "NO_IMPLICIT_DYNAMIC_CODE" at system.ads:44 This very likely means that the compiler is misconfigured. Try to replace "cygwin32" with "cygwin" in ada/gcc-interface/Makefile.in and rebuild the runtime (make al

Re: Successfull build of gcc-4.4.0 [trunk revision 145008] on i686-pc-cygwin

2009-03-25 Thread Rainer Emrich
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Eric Botcazou schrieb: >> For the acats tests most of the FAIL cases ar of the form: >> violation of restriction "NO_IMPLICIT_DYNAMIC_CODE" at system.ads:44 > > This very likely means that the compiler is misconfigured. Try to replace > "cygwin32" wi

Register Allocation Bug?

2009-03-25 Thread Kasper Bonne
Hi List (Sorry for the cross-post in gcc-bugs, I didn't look properly at the list before I posted). I have a question (or possible compiler bug) regarding inline assembly that I hope you can help me with. I wanted a routine that would give me the value and address of a memory location relative t

Re: Register Allocation Bug?

2009-03-25 Thread Andrew Haley
Kasper Bonne wrote: > > Since it hasn't been fixed maybe it's a bu..*ahem*..feature? It's a feature. Look up "earlyclobber" in the Fine Manual. Andrew.

Re: Should structure with flexible array be allowed to be passed by value?

2009-03-25 Thread H.J. Lu
On Tue, Mar 24, 2009 at 10:46 AM, Dave Korn wrote: > Brian Ellis wrote: >> struct dynamic { int size; int array[]; }; > >> int main() { struct dynamic * pBadness =  ((struct dynamic *) malloc( >> sizeof(int) * 3) ); > >> dont_do_this( *pBadness ); > > >  Are you even allowed to dereference a point

Re: Should structure with flexible array be allowed to be passed by value?

2009-03-25 Thread Joseph S. Myers
On Wed, 25 Mar 2009, H.J. Lu wrote: > gcc.c-torture/compile/pr16566-2.c has > > --- > struct A > { > int i; > int x[]; > }; > > int foo(struct A a) > { > return (a,a).x[0]; > } > --- > > foo will return a random number. I don't think it should be allowed. This is a perfectly ordina

Re: Register Allocation Bug?

2009-03-25 Thread Kasper Bonne
Hi Andrew On Wed, Mar 25, 2009 at 12:41, Andrew Haley wrote: >> Since it hasn't been fixed maybe it's a bu..*ahem*..feature? > > It's a feature.  Look up "earlyclobber" in the Fine Manual. I tried that already and it does work but I actually thought the 'earlyclobber' modifier was for situations

Re: Should structure with flexible array be allowed to be passed by value?

2009-03-25 Thread H.J. Lu
On Wed, Mar 25, 2009 at 6:37 AM, Joseph S. Myers wrote: > On Wed, 25 Mar 2009, H.J. Lu wrote: > >> gcc.c-torture/compile/pr16566-2.c has >> >> --- >> struct A >> { >>     int i; >>     int x[]; >> }; >> >> int foo(struct A a) >> { >>     return (a,a).x[0]; >> } >> --- >> >> foo will return a rando

Re: Register Allocation Bug?

2009-03-25 Thread Ian Lance Taylor
Kasper Bonne writes: > In my example the compiler should be able to figure out that the > register is not available for output (because it is used as input in > the following line), so if this behavior is not a bug, it should > be. IMO. This thread should really be on gcc-h...@gcc.gnu.org, not g

Re: Successfull build of gcc-4.4.0 [trunk revision 145008] on i686-pc-cygwin

2009-03-25 Thread Rainer Emrich
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Eric Botcazou schrieb: >> For the acats tests most of the FAIL cases ar of the form: >> violation of restriction "NO_IMPLICIT_DYNAMIC_CODE" at system.ads:44 > > This very likely means that the compiler is misconfigured. Try to replace > "cygwin32" wi

Re: Successfull build of gcc-4.4.0 [trunk revision 145008] on i686-pc-cygwin

2009-03-25 Thread Dave Korn
Rainer Emrich wrote: > Eric Botcazou schrieb: >>> For the acats tests most of the FAIL cases ar of the form: >>> violation of restriction "NO_IMPLICIT_DYNAMIC_CODE" at system.ads:44 >> This very likely means that the compiler is misconfigured. Try to replace >> "cygwin32" with "cygwin" in ada/gcc-

Re: Successfull build of gcc-4.4.0 [trunk revision 145008] on i686-pc-cygwin

2009-03-25 Thread Eric Botcazou
> I have these patches against 4.3.2/4.3.3 that should help with this. > (Sorry Eric, I've been too busy with the cygwin gcc distro releases to > start feeding these upstream yet, but they need to wait for 4.5 anyway. > They're not all in entirely suitable shape yet either.) Thanks for steppin

Re: Google Summer of Code 2009

2009-03-25 Thread Tobias Grosser
Hi Pranav, On Tue, 2009-03-24 at 23:32 +0530, Pranav wrote: > Hi Sebastian and Tobias, [...] > To delve deeper into compiler's research I will be joining the graduate > school at UIUC from next Fall. I feel that working on this project would > give me great pleasure and it would be the best wa

gcc-4.2-20090325 is now available

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

{gSoc}application : Automatic parallelization in Graphite

2009-03-25 Thread Li Feng
Hi all, Below is the proposal of this gSoc project. I'd really like you review and comment on this and then I can plan this project better. Thanks, Li Feng #title Automatic parallelization in Graphite * Syn