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]
Other format:	[Raw text]

Re: [DRAGONEGG] Expose 4 functions in i386.c

From: Jan Hubicka <hubicka at ucw dot cz>
To: Duncan Sands <baldrick at free dot fr>
Cc: Andrew Pinski <pinskia at gmail dot com>, gcc-patches <gcc-patches at gcc dot gnu dot org>
Date: Tue, 13 Apr 2010 18:16:55 +0200
Subject: Re: [DRAGONEGG] Expose 4 functions in i386.c
References: <4BC48E3C.50102@free.fr> <4107B37F-E19F-4140-AE3D-80CD0C267BC3@gmail.com> <4BC49626.3010707@free.fr>

> Hi Andrew,
>
>> Aren't at least one of these a target hook? Why can't you use the target
>> hooks?
>
> thanks for thinking about this.  As far as I can see none of these are target
> hooks.  Which one were you thinking of?  As for why I can't use target hooks,

These functions are used to implement x86-64 ABI (as you probably know). I.e. to tell
you where argument stays.  There are target hooks to pass these decisions into calls.c
via CUMULATIVE_ARGS, so search for these.

Honza

Follow-Ups:
- Re: [DRAGONEGG] Expose 4 functions in i386.c
  - From: Duncan Sands

References:
- [DRAGONEGG] Expose 4 functions in i386.c
  - From: Duncan Sands
- Re: [DRAGONEGG] Expose 4 functions in i386.c
  - From: Andrew Pinski
- Re: [DRAGONEGG] Expose 4 functions in i386.c
  - From: Duncan Sands

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