Displaying 5 results from an estimated 5 matches for "m86k".
Did you mean:
m68k
2013 Aug 09
2
[LLVMdev] [global-isel] Random comments on Proposal for a global instruction selector
...MPX that have 4 hardware bounds registers that need keeping in sync with pointers.
I am a bit skeptical about the need for pointer types; I don’t think it is the right level of abstraction for an instruction selector. The processors I know about with separate address and data registers (Blackfin, m86k, TriCore) would be modeled perfectly by the register bank labels in the proposal.
Won’t that work for your case?
Thanks,
/jakob
2013 Aug 10
0
[LLVMdev] [global-isel] Random comments on Proposal for a global instruction selector
...9 Aug 2013, at 22:15, Jakob Stoklund Olesen <stoklund at 2pi.dk> wrote:
> I am a bit skeptical about the need for pointer types; I don’t think it is the right level of abstraction for an instruction selector. The processors I know about with separate address and data registers (Blackfin, m86k, TriCore) would be modeled perfectly by the register bank labels in the proposal.
>
> Won’t that work for your case?
It might work, although given that our fat pointers are not integers I'm not sure how you think we should represent them. We can represent them as i256, but that would b...
2013 Aug 11
1
[LLVMdev] [global-isel] Random comments on Proposal for a global instruction selector
...13, at 22:15, Jakob Stoklund Olesen <stoklund at 2pi.dk> wrote:
>
>> I am a bit skeptical about the need for pointer types; I don’t think it is the right level of abstraction for an instruction selector. The processors I know about with separate address and data registers (Blackfin, m86k, TriCore) would be modeled perfectly by the register bank labels in the proposal.
>>
>> Won’t that work for your case?
>
> It might work, although given that our fat pointers are not integers I'm not sure how you think we should represent them. We can represent them as i256...
2013 Aug 09
0
[LLVMdev] [global-isel] Random comments on Proposal for a global instruction selector
On 9 Aug 2013, at 00:18, Jakob Stoklund Olesen <stoklund at 2pi.dk> wrote:
> I am hoping that this proposal will generate a lot of feedback, and there are many different topics to discuss. When replying to this email, please change the subject header to something more specific, but keep the [global-isel] tag.
Subject changed, but I'm not sure if helps...
Overall, I really like this
2013 Aug 08
14
[LLVMdev] [global-isel] Proposal for a global instruction selector
I am hoping that this proposal will generate a lot of feedback, and there are many different topics to discuss. When replying to this email, please change the subject header to something more specific, but keep the [global-isel] tag.
Thanks,
/jakob
Proposal for a Global Instruction Selector
It is becoming evident that we need a replacement for the SelectionDAG-based instruction selector. This