Displaying 5 results from an estimated 5 matches for "jaffrey".
2009 Jul 16
2
[LLVMdev] registers as home location
Thanks Eli, Jaffrey for the pointer!
A couple of further questions if I may
1. Isnt this assuming that register being pinned to is always esi when
it comes to using a calling convention.
I would like to pin the register through a pass and so I dont know
which registers ends up being used for a particular value befor...
2009 Jul 16
0
[LLVMdev] registers as home location
On Thu, Jul 16, 2009 at 2:41 PM, shreyas krishnan<shreyas76 at gmail.com> wrote:
> Thanks Eli, Jaffrey for the pointer!
>
> A couple of further questions if I may
> 1. Isnt this assuming that register being pinned to is always esi when
> it comes to using a calling convention.
You'd need a separate calling convention for each possible set of
registers pinned. The combinatoric possi...
2009 Jul 16
0
[LLVMdev] registers as home location
Chris recently wrote up a way to do this at
http://nondot.org/sabre/LLVMNotes/GlobalRegisterVariables.txt
On Thu, Jul 16, 2009 at 1:53 PM, shreyas krishnan<shreyas76 at gmail.com> wrote:
> Hi
> As part of a requirement that I have, I would like to have some
> globals reside in registers always. So these variables would not have
> a home location in memory.
> I realize the
2009 Jul 16
3
[LLVMdev] registers as home location
Hi
As part of a requirement that I have, I would like to have some
globals reside in registers always. So these variables would not have
a home location in memory.
I realize the code generated would also need to be aware of this. I do
have some ideas on how to change the code appropriately. But right
now, I am more concerned about how to fit this requirement (sort of
interprocedural) into the
2004 Jan 27
4
WARNING. You tried to send a potential virus or unauthorised code
The Star Internet anti-virus service, powered by MessageLabs,
discovered a possible virus or unauthorised code (such as a joke
program or trojan) in an email sent by you.
This email has now been quarantined and was not delivered.
Please read this whole email carefully. It explains what has happened
to your email, which suspected virus has been caught, and what to do if
you need help.
To