llvm dev - Aug 2009 - [LLVMdev] Win64 bugs

Hello, Nicolas
> Thanks a lot for the heads up. I hadn't run into any problems yet with
my
> hack because I haven't used other callee-saved registers so far.
Anyway, I'm
> looking forward to your fix!
I've commited the first series of patches to ToT to unbreak win64,
basically:

1. Honour register save area
2. Enable proper passing of __m128 and __m64 arguments
3. Minor cleanups here and there

The callee-saved problem is still unfixed, I'm working on general solution.

-- 
With best regards, Anton Korobeynikov
Faculty of Mathematics and Mechanics, Saint Petersburg State University

Thanks!

What revision is your commit? I'd like to have a closer look at your patch
in an attempt to understand the issue better, and maybe try fixing the
callee-saved problem.

Cheers,

Nicolas


-----Original Message-----
From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On
Behalf Of Anton Korobeynikov
Sent: woensdag 5 augustus 2009 9:35
To: LLVM Developers Mailing List
Subject: Re: [LLVMdev] Win64 bugs

Hello, Nicolas
> Thanks a lot for the heads up. I hadn't run into any problems yet with
my
> hack because I haven't used other callee-saved registers so far.
Anyway,
I'm
> looking forward to your fix!
I've commited the first series of patches to ToT to unbreak win64,
basically:

1. Honour register save area
2. Enable proper passing of __m128 and __m64 arguments
3. Minor cleanups here and there

The callee-saved problem is still unfixed, I'm working on general solution.

-- 
With best regards, Anton Korobeynikov
Faculty of Mathematics and Mechanics, Saint Petersburg State University
_______________________________________________
LLVM Developers mailing list
LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev

Hi Nicolas
> What revision is your commit? I'd like to have a closer look at your
patch
> in an attempt to understand the issue better, and maybe try fixing the
> callee-saved problem.
See r77962, r 77964 and around. But in fact there is nothing there
which indicates the issue :) It existed before my patches and exists
currently. We need to have some generic way to mark instructions
belonging to "frame setup code".

-- 
With best regards, Anton Korobeynikov
Faculty of Mathematics and Mechanics, Saint Petersburg State University