This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: What's the deal with MD_CALL_PROTOTYPES ?
- To: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
- Subject: Re: What's the deal with MD_CALL_PROTOTYPES ?
- From: Jeffrey A Law <law@cygnus.com>
- Date: Wed, 11 Aug 1999 01:57:19 -0600
- cc: egcs@egcs.cygnus.com
- Reply-To: law@cygnus.com
In message <199908101743.NAA21180@caip.rutgers.edu>you write:
> So I'm prototyping stuff in insn-* and I notice that the macro
> MD_CALL_PROTOTYPES wraps gen_call() and gen_call_value() in
> insn-flags.h. The docs says this:
>
> > `MD_CALL_PROTOTYPES'
> > Define this if you wish to generate prototypes for the `gen_call'
> > or `gen_call_value' functions generated from the machine
> > description file. If `USE_PROTOTYPES' is defined to be 0, or the
> > host compiler does not support prototypes, or `NO_MD_PROTOTYPES'
> > is defined, this macro has no effect. As soon as all of the
> > machine descriptions are modified to have the appropriate number
> > of arguments, this macro will be removed.
>
> So I was wondering can it be removed? Judging from the insn-flags.h
> vs insn-emit.c output, it looks like Irix6 gets it right, but not
> solaris2.
I'd prefer not to remove it. Instead we should be looking to fix the various
backends so that we can enable prototypes for the gen_call* functions.
jeff