usefulness of NO_ARGS_ARRAY

usefulness of NO_ARGS_ARRAY

[Dan Nicolaescu]

NO_ARGS_ARRAY is currently only used on 32bit x86 non-MS Windows machines.
It's doubtful that the few instructions saved make any difference on
modern machines...

NO_ARGS_ARRAY assumes that function arguments are passed on the stack,
but that is not true when using the -mregparam option, or when the
compiler decides to change the calling convention (like gcc-4.5 can
when using -flto).

Do we still want to keep NO_ARGS_ARRAY?

Re: usefulness of NO_ARGS_ARRAY

[Andreas Schwab]

Dan Nicolaescu <dann@gnu.org> writes:

> NO_ARGS_ARRAY is currently only used on 32bit x86 non-MS Windows machines.
  NO_ARG_ARRAY

Every modern system needs to define it.

> NO_ARGS_ARRAY assumes that function arguments are passed on the stack,

ITYM !NO_ARG_ARRAY.

> Do we still want to keep NO_ARGS_ARRAY?

IMHO it should always be defined and consequently removed.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: usefulness of NO_ARGS_ARRAY

[Dan Nicolaescu]

Andreas Schwab <schwab@linux-m68k.org> writes:

> Dan Nicolaescu <dann@gnu.org> writes:
>
>> NO_ARGS_ARRAY assumes that function arguments are passed on the stack,
>
> ITYM !NO_ARG_ARRAY.

Exactly.

>> Do we still want to keep NO_ARGS_ARRAY?
>
> IMHO it should always be defined and consequently removed.

That's what I want to do, I'll do that in a week or so if there's no
objection until then.