search for: short_desc_typ

...cgi?bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&field0-0-0=noop&type0-0-0=noop&value0-0-0=&namedcmd=All+Bugs&namedcmd=All+Bugs&namedcmd=All+Bugs&newqueryname=&newqueryname=Open+Bugs&order=Date Have anybody...

Hi Valery, On Tue, 2007-04-10 at 13:15 +0200, Valery Khamenya wrote: > Hi, > > where could one find any LLVM development roadmap for this > and perhaps next year? About the best "roadmap" we have is the list of enhancements in Bugzilla: http://llvm.org/bugs/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_sta...

...ould post the snippet of LLVM assembly code that is miscompiled, that will help us figure out if LLVM was/is miscompiling your program. Also, you can check the following URL for X86 Backend bugs to see if your code could be triggering the following bugs: http://llvm.cs.uiuc.edu/bugs/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&component=X86+Backend&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=RESOLVED&ema...

Hi, where could one find any LLVM development roadmap for this and perhaps next year? Especially would be interesting to know about * planned features for PS3 Cell processor -- as well as for Wii, Xbox360 CPUs * multithreading in general * possibly coming changes in major versioning and related issues * other interesting featuring comments on current status to above listed items are also

Chris, I'm fine with using JIT, but I'm trying to understand this problem: 1. My LLVM program does not produce correct results 2. Using llvm-dis, I disassemble the bytecode to C 3. I recompile using GCC and the program _works correctly_. The only odd thing is when I recompile with GCC, I see these messages: pal3.c:195: warning: conflicting types for built-in function `strcmp'