Re: gdbarch.c problem building for cygwin

[Andrew Cagney <ac131313 at cygnus dot com>]

Mark Kettenis wrote:
> 
>    Date: Mon, 12 Jun 2000 09:50:06 +1000
>    From: Andrew Cagney <ac131313@cygnus.com>
> 
>    Chris Faylor wrote:
> 
>    > FIX_CALL_DUMMY expands to a { .. } block on i386 so this doesn't
>    > work too well.  Changing the line to this:
>    >
>    > XSTRING ((FIX_CALL_DUMMY (dummy, pc, fun, nargs, args, type, gcc_p))));
>    >
>    > "fixes" the problem but I fear that we would just be using a gcc
>    > specific extension by doing this.
> 
>    Very gcc specific.  I'll go through and see which ones can't be
>    expanded, sigh.
> 
> The obvious solution is of course to change FIX_CALL_DUMMY for the
> i386 :-).  I'll turn it into a proper function in i386-tdep.c, and
> change config/i386/tm-i386.h accordingly.  That wouldn't fix
> i[3456]86-*-sunos* but we've almost decided that that one is obsolete
> :-).

:-)

I've checked in the attached.  It stops the dump when the function is
void and things aren't multi-arch.

	Andrew