search for: simple_switch

Displaying 4 results from an estimated 4 matches for "simple_switch".

2008 Apr 21
3
[LLVMdev] Whole-function isel
...turnBlock: ; preds = %entry ret i32 %z } And here's the X86 DAG right before it gets fed one BB at a time into pre-RA scheduling. Each color is a different basic block. Cheers! -- Chris -------------- next part -------------- A non-text attachment was scrubbed... Name: simple_switch.pdf Type: application/pdf Size: 33075 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20080420/fa2c55e7/attachment.pdf>
2008 Apr 22
0
[LLVMdev] Whole-function isel
...ret i32 %tmp8 > UnifiedReturnBlock: ; preds = %entry > ret i32 %z > } > > And here's the X86 DAG right before it gets fed one BB at a time > into pre-RA scheduling. Each color is a different basic block. > > Cheers! > -- > Chris > > <simple_switch.pdf>_______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
2008 Mar 25
0
[LLVMdev] Whole-function isel
On Mar 24, 2008, at 10:47 PM, Christopher Lamb wrote: > I know that this has been discussed (at least in passing) a few > times on the list, but I couldn't locate a bug for it. Have any > architectural plans been made for it? Funny you bring this up. Evan and I were tossing around crazy ideas about this just today. If you're interested, maybe we should get together for
2008 Mar 25
4
[LLVMdev] Whole-function isel
I know that this has been discussed (at least in passing) a few times on the list, but I couldn't locate a bug for it. Have any architectural plans been made for it? Are there architectural roadblocks with the current LLVM infrastructure that will complicate the process? What has demotivated the implementation of this so far (is it not that big a benefit on important targets, too