Displaying 4 results from an estimated 4 matches for "_idea_".
2007 Apr 11
1
[LLVMdev] LLVM Roadmap 2007-2008, PowerPC, multithreading, LLVM 2.0, etc ?
...they are
> needed. Lately it seems that this means lots of inline asm bug fixes. :)
> In the next month or two, I'd like to finish up our C++ EH implementation,
> ideally for 2.0, but (again) no promises :).
well, it should be definitely not about promises at all,
but about getting _idea_ where LLVM currently is and where
it is going to. Many ppl outside of LLVM development process
will not bother big LLVM guys-n-girls via chat. And
they likely to go on with their business further without
getting a right point about how cool LLVM is, and how cool
LLVMdevers going to make LLVM in...
2007 Apr 10
0
[LLVMdev] LLVM Roadmap 2007-2008, PowerPC, multithreading, LLVM 2.0, etc ?
On Tue, 10 Apr 2007, Valery Khamenya wrote:
> where could one find any LLVM development roadmap for this
> and perhaps next year?
We generally have not published a road map like this because it is very
difficult to do it in a meaningful way. Because LLVM is largely driven by
volenteers and because noone working on it guarantees that they will
finish a project that they start, we
2007 Apr 10
6
[LLVMdev] LLVM Roadmap 2007-2008, PowerPC, multithreading, LLVM 2.0, etc ?
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
2008 Mar 03
5
on the philosophical aspects of a specification
a specification will _eventually_ be used, by someone,
to tell the user they are doing things "wrong", won't it?
and doesn't that turn markdown's genesis upside-down?
heck, next thing you know we'll be telling them to r.t.f.m.
i would prefer that implementers get more sophisticated
about teasing out the user's intent in "ambiguous" cases.
of course,