<html><head><style type="text/css">body {word-wrap: break-word; background-color:#ffffff;}</style></head><body><div style="font-family: sans-serif; font-size: 16px">I think that you need two things:<br><br>1. A direct-as-possible mapping in between the DAG and the stub backend instructions<br><br>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.<br><br> -Hal<br><br><font color="#333333"><i><span style="font-size: 14px"><font face="sans-serif">Sent from my Verizon Wireless Droid</font></span></i></font></div><br><br>-----Original message-----<br><blockquote style="; border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><div style="font-family: sans-serif; font-size: 14px"><b>From: </b>Anton Korobeynikov <anton@korobeynikov.info><b><br>To: </b>Jakob Stoklund Olesen <stoklund@2pi.dk><b><br>Cc: </b>llvmdev@cs.uiuc.edu<b><br>Sent: </b>Tue, Jul 10, 2012 22:09:01 GMT+00:00<b><br>Subject: </b>Re: [LLVMdev] New backend<br><br></div>>>> Are there any plans to this?<br>>>> I'd like to see a 'stub' backend in the llvm-tree (or somewhere else).<br>>> Well, I asked on the list previously, but noone ever responded….<br>> Don't targets like MSP430 and MBlaze serve as good stubs?<br>It's a good question... I think people are looking for something<br>minimal, so they already know that there are no "unnecessary" stuff...<br><br>-- <br>With best regards, Anton Korobeynikov<br>Faculty of Mathematics and Mechanics, Saint Petersburg State University<br><br>_______________________________________________<br>LLVM Developers mailing list<br>LLVMdev@cs.uiuc.edu <a href="http://llvm.cs.uiuc.edu">http://llvm.cs.uiuc.edu</a><br><a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev">http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev</a><br></blockquote></body></html>