Displaying 20 results from an estimated 4000 matches similar to: "[LLVMdev] LLVM GC"
2011 Jan 15
2
[LLVMdev] Fw: LLVM GC
Forgot to CC the list.
----- Forwarded Message ----
> From: Samuel Crow <samuraileumas at yahoo.com>
> To: Trevor Elliott <trevor at galois.com>
> Sent: Fri, January 14, 2011 7:33:15 PM
> Subject: Re: [LLVMdev] LLVM GC
>
> Hi Trevor,
>
> Are you linking with LibStdC++ or LibC++? That is a requirement for running
> code that has been compiled from C++
2011 Jan 17
0
[LLVMdev] Fw: LLVM GC
Hi Sam,
I've not actually gotten to the linking process with my runtime, as I've
compiled it with clang -emit-llvm -c, and then archived it with llvm-ar
and llvm-ranlib. I'm also not producing a GC plugin, as I'm using the
builtin "shadow-stack" strategy.
My current build process looks like this:
1. build the compiler
2. build the runtime using clang -emit-llvm -c
2011 Jan 19
0
[LLVMdev] Shadow Stack
Hi Everyone,
I've managed to create a small example that reproduces the error that
I'm seeing when generating code, or running the interpreter:
-----------------------------------------------------------------------
@llvm_gc_root_chain = global i8* null
declare i8* @malloc(i32)
declare void @llvm.gcroot(i8**, i8*) nounwind
define i32 @main() gc "shadow-stack" {
%value =
2016 Dec 27
1
Running grep with LLI
Hi everyone,
I compiled grep with llvm-3.4(because consumer tool uses llvm3.4 bit code)
and generate bit-code for this.
When I am running with lli output is
pseudo instructions should be removed before code emission
UNREACHABLE executed at
/home/awanish/llvm/llvm-3.4.2/lib/Target/X86/X86CodeEmitter.cpp:1176!
0 libLLVM-3.4.so 0x00007f1250f655d5
llvm::sys::PrintStackTrace(_IO_FILE*) + 37
1
2010 Jul 16
2
[LLVMdev] Function::getName in CallGraphSCCPass causes bus error
Hi,
I'm trying to use CallGraphSCCPass, but I keep getting a bus error. I
can reproduce the problem quite easily using the lib/Transforms/Hello
example. I simply mix in these changes:
#include "llvm/CallGraphSCCPass.h"
...
struct Hello : public CallGraphSCCPass {
static char ID; // Pass identification, replacement for typeid
Hello() : CallGraphSCCPass(&ID) {}
2010 Jun 12
0
[LLVMdev] experimenting with partial evaluation
Good evening, Pierre.
Here is an example to you. attached. run with -disable-lazy-comilation.
It is *as-is* for Win32 but might be applicable to *-linux-elf more smartly.
It does get llvm::Function* by function ptr(not name!),
and clone a specialized function,
and execute specialized one
in the same context as parent lli.
> - In a running program, can I get pointers to the llvm Module that
2010 Jun 11
2
[LLVMdev] experimenting with partial evaluation
Hello !
I wanted to experiment with partial evaluation and llvm seems to be the
right tool for this, but since I'm new to it of course I'm a bit lost !
I'll try to explain what I want to do in the simplest possible way :
I have a C program.
In this program, there is a function f( a,b ).
I have a value A for a.
I want to specialise f() so I get a function fA( b ) which is the same as
2011 Mar 29
1
[LLVMdev] cross compiling to sparc with llvm
Hi,
I'm trying to use llvm/clang to cross compile to sparcv9. The following
works with a -march=sparc, but yields errors for sparcv9. Are there some
other flags that need to be specified?
Thanks,
Tarun
> clang -m64 -emit-llvm test.c -c -o test.bc
> llc -march=sparcv9 test.bc -o hello.s
ExpandIntegerResult #0: 0x8a6c478: i64 = GlobalAddress<[4 x i8]* @.str> 0
[ORD=1] [ID=0]
Do
2012 Jan 12
3
[LLVMdev] 'opt' Aborted "While deleting: void %"
Hey everyone,
So I have an LLVM pass that appears to run completely and work fine, and
then it aborts at the very end. When exiting the final runOnFunction call,
I get the following error / stack dump. I cannot figure out why this is
happening for the life of me - does anyone have any ideas? I'm not trying
to do any crazy deallocation or anything, it just seems like a normal pass
to me.
2012 Jan 12
0
[LLVMdev] 'opt' Aborted "While deleting: void %"
Hi Griffin, did your pass create a data structure that holds values somehow,
and forgot to delete it? Also, try running under valgrind in case this is
due to a memory error of some kind.
Ciao, Duncan.
> So I have an LLVM pass that appears to run completely and work fine, and
> then it aborts at the very end. When exiting the final runOnFunction call,
> I get the following error /
2012 Jan 13
1
[LLVMdev] 'opt' Aborted "While deleting: void %"
Using Valgrind hasn't shown me anything terribly unusual. And I'm confused
because its not even trying to delete a real instruction; deleting a void
type with no name? That doesn't make any sense...
Any other hints? I've seen a few posts in the past about this relating to
some internal LLVM bugs...
-Griffin
On Thu, 12 Jan 2012 21:26:41 +0100, Duncan Sands <baldrick at
2012 Feb 03
3
[LLVMdev] How can I see what opt tries to delete at the end of a pass?
Hello,
I've been stuck with a problem for about a month, and it has stumped
everyone in my lab. I have a function pass that runs, and when it finishes
and opt goes to return, I get:
While deleting: void %
An asserting value handle still pointed to this value!
UNREACHABLE executed at /x/grwright/llvm/llvm-2.9/lib/VMCore/Value.cpp:569!
On a simple test case, the error becomes 'i32 %'
2012 May 16
2
[LLVMdev] NVPTX: __iAtomicCAS support ?
Dear colleagues,
I'm looking if we can replace nvopencc with LLVM NVPTX in our project.
It turns NVPTX won't work with the code nvopencc can handle (please
see the log below). So are atomic intrinsics not supported or am I
doing call in a wrong way?
Thanks,
- Dima.
SOURCE
========
dmikushin at hp2:~> cat kernelgen_monitor.ll
; ModuleID =
2014 May 12
2
[LLVMdev] Name of the libraries + soname? 3.4.1 ?
On 12/05/2014 15:22, Tom Stellard wrote:
> On Mon, May 12, 2014 at 08:41:36AM +0200, Sylvestre Ledru wrote:
>> Hello,
>>
>> With the release of 3.4.1, the LLVM library has been renamed from
>> libLLVM-3.4.so to libLLVM-3.4.1.so. In parallel, the soname has been
>> updated to
>> reflect this change.
>>
>> AFAIK, we kept the ABI compatible from 3.4
2012 Sep 03
2
[LLVMdev] [NVPTX] Backend cannot handle array-of-arrays constant
Dear all,
Looks like the NVPTX backend cannot handle array-of-arrays contant
(please see the reporocase below). Is it supposed to work? Any ideas
how to get it working? Important for our target applications.
Thanks,
- Dima.
$ cat test.ll
; ModuleID = '__kernelgen_main_module'
target datalayout =
2012 May 16
0
[LLVMdev] NVPTX: __iAtomicCAS support ?
> -----Original Message-----
> From: Dmitry N. Mikushin [mailto:maemarcus at gmail.com]
> Sent: Wednesday, May 16, 2012 5:44 AM
> To: LLVM-Dev
> Cc: Justin Holewinski
> Subject: NVPTX: __iAtomicCAS support ?
>
> Dear colleagues,
>
> I'm looking if we can replace nvopencc with LLVM NVPTX in our project.
> It turns NVPTX won't work with the code nvopencc
2012 Jun 25
2
[LLVMdev] Is llc broken for Cortex-A9 + neon ?
Hi all,
considering following .ll file
; ModuleID = 'vect3x.ll'
target triple = "armv7-none-linux-gnueabi"
define arm_aapcscc void @test_hi_char8(i8* %.T0351, <8 x i8>* nocapture %srcA, <4 x i8>* nocapture %dst) noinline {
L.entry:
%0 = tail call arm_aapcscc i32 (...)* @get_global_id(i8* %.T0351, i32 0)
%1 = bitcast <8 x i8>* %srcA to <4 x i8>*
2011 Dec 12
4
[LLVMdev] problem with runOnLoop
hi all,
I want access to all basic blocks of function in a loop, so I used the
following code:
*bool parallel::runOnLoop(Loop *L, LPPassManager &LPM)
{
for (Function::iterator bi= func->begin(); bi != func->end(); bi++){
//
}
}*
First loop run without problem, but for second loop I get the following
error:
*0 libLLVM-2.9.so 0x0137d530
1 libLLVM-2.9.so 0x0137fa6c
2
2012 Jun 25
0
[LLVMdev] Is llc broken for Cortex-A9 + neon ?
Sounds like a bug in vector promote. If I restore this flag and use
-promote-elements=0 everything works for me.
Please fill a PR in LLVM bugzilla and assign to Nadav.
On Mon, Jun 25, 2012 at 5:04 PM, Sebastien DELDON-GNB
<sebastien.deldon at st.com> wrote:
> Hi all,
>
>
> considering following .ll file
>
> ; ModuleID = 'vect3x.ll'
> target triple =
2012 Sep 04
0
[LLVMdev] [NVPTX] Backend cannot handle array-of-arrays constant
NVCC successfully handles the same IR, if we try to process the same
.cu file with clang+nvptx and nvcc:
CLANG/NVPTX:
=============
$ cat dayofweek.cu
__attribute__((device)) char yweek[7][4] = { "MON", "TUE", "WED",
"THU", "FRI", "SAT", "SUN" };
$ clang -cc1 -emit-llvm -fcuda-is-device dayofweek.cu -o dayofweek.ll
$ cat