[LLVMdev] New backend

[Hal Finkel]

I think that you need two things:

1. A direct-as-possible mapping in between the DAG and the stub backend instructions

2. The features of the backend are all configurable (legal datatypes and instructions, what is promoted to what, etc.) so that we can test as much of the legalizer's parameter space as possible.

 -Hal

Sent from my Verizon Wireless Droid

-----Original message-----
From: Anton Korobeynikov <anton at korobeynikov.info>
To: Jakob Stoklund Olesen <stoklund at 2pi.dk>
Cc: llvmdev at cs.uiuc.edu
Sent: Tue, Jul 10, 2012 22:09:01 GMT+00:00
Subject: Re: [LLVMdev] New backend

>>> Are there any plans to this?
>>> I'd like to see a 'stub' backend in the llvm-tree (or somewhere else).
>> Well, I asked on the list previously, but noone ever responded….
> Don't targets like MSP430 and MBlaze serve as good stubs?
It's a good question... I think people are looking for something
minimal, so they already know that there are no "unnecessary" stuff...

-- 
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120710/4f27d033/attachment.html>