This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] Remove DUP_PASS macro

From: Brian Booth <bbooth at redhat dot com>
To: Giovanni Bajo <giovannibajo at libero dot it>
Cc: GCC-Patches <gcc-patches at gcc dot gnu dot org>
Date: Fri, 23 Jul 2004 14:28:17 -0400
Subject: Re: [PATCH] Remove DUP_PASS macro
References: <1090603941.8134.155.camel@toss-off.toronto.redhat.com> <05d801c470dd$9f383200$30402597@bagio>

On Fri, 2004-07-23 at 13:51, Giovanni Bajo wrote:
> Brian Booth wrote:
> +  0     /* in_pass_list */
> 
> Why do we need this for every pass? Can't we just leave it out the initializer
> so that it gets default-initialized to 0? Maybe you can document that it has to
> stay at the bottom of the structure.

I would, but if I leave it out, bootstrap fails with the following
warning:

/notnfs/bbooth/gcc_work/dup_pass/gcc/gcc/tree-optimize.c:77: warning:
missing initializer
/notnfs/bbooth/gcc_work/dup_pass/gcc/gcc/tree-optimize.c:77: warning:
(near initialization for `pass_gimple.in_pass_list')
make[2]: *** [tree-optimize.o] Error 1
make[2]: Leaving directory `/notnfs/bbooth/gcc_work/dup_pass/build/gcc'
make[1]: *** [stage2_build] Error 2
make[1]: Leaving directory `/notnfs/bbooth/gcc_work/dup_pass/build/gcc'
make: *** [bootstrap] Error 2

Brian

References:
- [PATCH] Remove DUP_PASS macro
  - From: Brian Booth
- Re: [PATCH] Remove DUP_PASS macro
  - From: Giovanni Bajo

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]