Displaying 9 results from an estimated 9 matches for "litb".
Did you mean:
lib
2011 Mar 19
0
[LLVMdev] [Patch] Fix bug in llvm::SmallVectorIml<>::insert
Johannes Schaub (litb) wrote:
> This fixes a bug in SmallVectorImpl<>::insert, which were not behaving
> correctly on inserting an empty range into an empty vector:
>
> #include <llvm/ADT/SmallVector.h>
> #include <cassert>
>
> int main() {
> llvm::SmallVector<int, 1>...
2011 Mar 19
2
[LLVMdev] [Patch] Fix bug in llvm::SmallVectorIml<>::insert
This fixes a bug in SmallVectorImpl<>::insert, which were not behaving
correctly on inserting an empty range into an empty vector:
#include <llvm/ADT/SmallVector.h>
#include <cassert>
int main() {
llvm::SmallVector<int, 1> v, w;
llvm::SmallVector<int, 1>::iterator it =
v.insert(v.end(), w.begin(), w.end());
assert(it == v.end());
}
The insert function(s)
2011 Mar 24
0
[LLVMdev] Is LLVM appropriate for implementing a shell interpreter?
Mu Qiao wrote:
> Hi devs,
>
> We are implementing a library that interprets shell scripts so that
> other programs could efficiently talk to bash. We'd like to hear your
> advice on whether LLVM is appropriate for us. Here are our considerations:
>
> In most cases our library will interpret each script just once. Our
> current approach is using a manual
2011 Mar 24
2
[LLVMdev] Is LLVM appropriate for implementing a shell interpreter?
Hi devs,
We are implementing a library that interprets shell scripts so that
other programs could efficiently talk to bash. We'd like to hear your
advice on whether LLVM is appropriate for us. Here are our considerations:
In most cases our library will interpret each script just once. Our
current approach is using a manual implementation based on ANTLR and
C++, so actually we are executing
2011 Mar 19
0
[LLVMdev] [Patch] Fix for PR9499 (confusing behavior of FastFoldingSetNode).
I've made a patch which provides one possible fix for the unintuitive
behavior of FastFoldingSetNode. I'm not sure whether that's a good way to
solve this. It's based largely on the documentation found in the
FastFoldingSet.h file, which says Profile functions should use "Add" instead
of simply setting their parameter.
Patch is attached on this mail and on the PR.
2011 Apr 06
0
[LLVMdev] Prevent merging of names to types
Hello all,
in my runtime lowlevel IR module I have several type definitions, some of
which may turn out to be structurally equivalent. They look like follows
%enumeration_ty = type {
; count of enumerators
i32,
; enumerators
[0 x %enumerator_ty]
}
%lookupresult_ty = type {
; kind of lookup result
i32,
i8*
}
Now when I link this module to the code generation module
2011 Apr 20
0
[LLVMdev] Is this a bug in clang?
Ahmed Charles wrote:
> Technically, it could've sent the mail before you even thought about
> writing it. Undefined is undefined, there are no requirements. From:
> Dustin Laurence
> Sent: Wednesday, April 20, 2011 6:50 AM
> To: llvmdev at cs.uiuc.edu
> Subject: Re: [LLVMdev] Is this a bug in clang?
> On 04/19/2011 10:50 PM, John Regehr wrote:
>
>> The compiler
2011 Jul 25
0
[LLVMdev] Memory leaks in the JIT and how will MC-objects be deallocated in the MCJIT?
We are currently using the JIT (non-MC) to implement a REPL-like shell that
needs to run in a long-lived process. During development, we noticed
substantial memory-growth with increased lifetime of the JIT.
In trying to eliminate that continuous memory growth, we did a few things,
including making LLVMContext collect and free unused constants (detected by
Value::uses_empty()). This dropped
2011 Apr 06
2
[LLVMdev] Target independency using "opaque"? How to do it else?
Hello all,
I'm writing a backend for our scriptlanguage compiler and I'm currently
writing an IR module for the runtime library that contains some support
routines called by generated code.
The IR module contains calls to "malloc", which depend on the size of
"size_t". Since I don't know the target when writing the IR module for the
runtime library, I