Kai,
did you make your diff against the current CVS checkout or against
your first patch? Should your changes already work for some cases? I
would like to test if they produce the right instructions. However, I
do not have enough insight into gcc to work on it myself.
Thanks,
Nicolas
On A
Hi Kai,
so, could you resolve the remaining issues? Or have you kind of
paused the project?
Cheers,
Nicolas
On Jul 12, 2007, at 2:14 , Kai Tietz wrote:
Hi,
I am nearly through :) The remaining macros left to be ported are
REGPARM_MAX and SSE_REGPARM_MAX. The sysv_abi uses 6 regs and 8 ss
Ok - so question is if x86_64 is completely implemented already. For
our case, especially the MS ABI. Andrew, do you have any knowledge if
they introduced a new calling convention and how they named it?
Nicolas
On Jul 10, 2007, at 13:29 , Andrew Pinski wrote:
On 7/10/07, Nicolas Alt
That's cool! What version would you do the patch for?
Apart from wine, I guess mingw should have the biggest need for the
MS ABI in order to support AMD64.
Nicolas
On Jul 10, 2007, at 5:59 , Kai Tietz wrote:
Windows and GCC ABIs are on x86-64 more different than that (they
was
historicall
, Nicolas Alt wrote:
Hi!
On the AMD64 / x86-64Bit architecture, some arguments of a functions
are passed using registers, but there seem to be two different
conventions out there. The standard ABI uses 6 registers, but
Microsoft compilers use only 4. Because of that, code compiled with
gcc cannot call
wpaul/winx64_wrap.S
On Jul 9, 2007, at 12:58 , Dave Korn wrote:
On 09 July 2007 20:48, Nicolas Alt wrote:
Hi!
On the AMD64 / x86-64Bit architecture, some arguments of a functions
are passed using registers, but there seem to be two different
conventions out there. The standard ABI uses 6 registers
Hi!
On the AMD64 / x86-64Bit architecture, some arguments of a functions
are passed using registers, but there seem to be two different
conventions out there. The standard ABI uses 6 registers, but
Microsoft compilers use only 4. Because of that, code compiled with
gcc cannot call code co