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]

Re: ANSI C compiler required to build GCC from CVS?


On Sep 18, 2000, Albert Chin-A-Young <china@thewrittenword.com> wrote:

> -     void (*loop_dump_aux)(const struct loop *, FILE *, int);
> +     void (*loop_dump_aux)();

Actually, we have a different way to deal with this problem, so that
we don't miss the prototypes on compilers that support them.  I'm
checking this in, under the ``obviously correct'' rule.

Index: gcc/ChangeLog
from  Alexandre Oliva  <aoliva@redhat.com>

	* flow.c (flow_loops_dump): Use PARAMS for prototypes.

Index: gcc/flow.c
===================================================================
RCS file: /cvs/gcc/egcs/gcc/flow.c,v
retrieving revision 1.339
diff -u -p -r1.339 flow.c
--- gcc/flow.c 2000/09/12 17:54:19 1.339
+++ gcc/flow.c 2000/09/18 08:30:54
@@ -7399,7 +7399,7 @@ void 
 flow_loops_dump (loops, file, loop_dump_aux, verbose)
      const struct loops *loops;
      FILE *file;
-     void (*loop_dump_aux)(const struct loop *, FILE *, int);
+     void (*loop_dump_aux) PARAMS ((const struct loop *, FILE *, int));
      int verbose;
 {
   int i;

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist    *Please* write to mailing lists, not to me

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