On Jun 30, 2011, at 1:21 PM, Richard Henderson wrote:
> On 06/29/2011 04:01 PM, Steven Bosscher wrote:
>> How many TARGET_ASM_FUNCTION_{PRO,EPI}LOGUE targets are left anyway?
>
> Answering the question that it sounds like you actually asked: 2 or 3.
> Not that it does us that much good because of
On 06/29/2011 04:01 PM, Steven Bosscher wrote:
> How many TARGET_ASM_FUNCTION_{PRO,EPI}LOGUE targets are left anyway?
Answering the question that it sounds like you actually asked: 2 or 3.
Not that it does us that much good because of the other uses.
FWIW, Alpha appears to be the only target that
On 06/29/2011 04:01 PM, Steven Bosscher wrote:
> Can you please also update http://gcc.gnu.org/backends.html? I think
> VAX should have a 'g' after you commit this patch.
Sure.
> How many TARGET_ASM_FUNCTION_{PRO,EPI}LOGUE targets are left anyway?
It's difficult to tell at a glance, because quit
On Wed, Jun 29, 2011 at 11:49 PM, Richard Henderson wrote:
> --- a/gcc/config/vax/vax.c
> +++ b/gcc/config/vax/vax.c
> @@ -70,9 +69,6 @@ static int vax_return_pops_args (tree, tree, int);
> #undef TARGET_ASM_ALIGNED_HI_OP
> #define TARGET_ASM_ALIGNED_HI_OP "\t.word\t"
>
> -#undef TARGET_ASM_FUNC
Not that there's much rtl to emit, since the CALL instruction
interpreting the procedure entry mask does almost all the work.
However, it means we're no longer emitting dwarf2 via the
text-based entry points.
---
gcc/config/vax/vax-protos.h |1 +
gcc/config/vax/vax.c| 86
