search for: upstrream

Displaying 5 results from an estimated 5 matches for "upstrream".

Did you mean: upstream
2008 Oct 07
2
[LLVMdev] Making Sense of ISel DAG Output
...get it to even accept and generate mostly-correct code for the pattern, I'm going to need a little help from the tblgen experts to get this final cleanup accomplished. How should that happen? Does SelectNodeTo need to take care of it? I plan to contribute these enhancements to tblgen back upstrream as they are quite useful for doing cool isel stuff. But I gotta get this case to work first. :) -Dave
2008 Mar 08
2
pdflatex: fuzzy fonts in Evince, but not on paper output
Hi, I've been using LaTeX for a few years on Mac OS X, and I'd like to use it on CentOS now. I installed a complete environment using 'yum groupinstall "Authoring and Publishing"' and then installing tetex-xdvi, plus manually installing the 'memoir' class. I can run 'latex document.tex' ok: the resulting .dvi looks nice in xdvi. When running
2008 Oct 07
0
[LLVMdev] Making Sense of ISel DAG Output
...his case. If that's not working, it's a bug. What version of LLVM are you using here? This is code that has changed substantially over the last few months. And we've fixed a number of similar-sounding bugs along the way. > > I plan to contribute these enhancements to tblgen back upstrream as > they are > quite useful for doing cool isel stuff. But I gotta get this case > to work > first. :) :-) Dan
2008 Oct 03
0
[LLVMdev] Making Sense of ISel DAG Output
On Fri, October 3, 2008 9:10 am, David Greene wrote: > On Thursday 02 October 2008 19:32, Dan Gohman wrote: > >> Looking at your dump() output above, it looks like the pre-selection >> loads have multiple uses, so even though you've managed to match a >> larger pattern that incorporates them, they still need to exist to >> satisfy some other users. > > Yes,
2008 Oct 03
3
[LLVMdev] Making Sense of ISel DAG Output
On Thursday 02 October 2008 19:32, Dan Gohman wrote: > Looking at your dump() output above, it looks like the pre-selection > loads have multiple uses, so even though you've managed to match a > larger pattern that incorporates them, they still need to exist to > satisfy some other users. Yes, I looked at that too. It looks like these other uses end up being chains to