Displaying 20 results from an estimated 1000 matches similar to: "[LLVMdev] Calling LLVM API from within an llvm::Module"
2008 Feb 11
1
unable to delete epoll event: Bad file
I know this error has been reported before, but a couple ppl have
reported getting this randomly when running Thin and it crashed the
server:
terminate called after throwing an instance of ''std::runtime_error''
what(): unable to delete epoll event: Bad file descriptor
I think it''s fixed on trunk now so I''m telling people that have this
issue to checkout
2007 Jan 23
0
[853] trunk/wxruby2/swig: Replace deprecated STR2CSTR with StringValuePtr
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head><meta http-equiv="content-type" content="text/html; charset=utf-8" /><style type="text/css"><!--
#msg dl { border: 1px #006 solid; background: #369; padding:
2007 Jun 25
0
[1069] trunk/wxruby2/swig/typemap.i: Fix big memory leak in methods taking wxString as a parameter
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head><meta http-equiv="content-type" content="text/html; charset=utf-8" /><style type="text/css"><!--
#msg dl { border: 1px #006 solid; background: #369; padding:
2004 Nov 06
3
Calling CreateFile on an instance of File - possible?
Hi all,
I''m going over win32-file this weekend. I''m creating instance methods for
setting (or unsetting) the various file attributes. So, you can do
something like:
f = File.open("foo.txt")
f.archive = true
f.hidden = true
f.close
This works for the basic attributes, but it requires extra work for others.
Specifically, I am having trouble trying to set the
2014 Dec 02
3
[LLVMdev] Questions about deallocation responsibilities
I am, from a front end, calling functions like LLVMModuleCreateWithName, found
in Core.h, ultimately calling LLVMWriteBitcodeToFile, found in BitWriter.h.
Do I correctly presume, from the existence of LLVMDisposeModule, that
I am responsible for calling it when I'm done? Will I need to do deeper
disposing myself? I presume at least I will need to free strings I allocated
myself, such as the
2009 Jul 18
2
[LLVMdev] Where does llvm.memcpy.i64 and friends get lowered ?
I am iterating through Modules symbols for 'test/CodeGen/X86/memcpy.bc
I get :-
---------- Functions ----------
llvm.memcpy.i64
Mangled name = llvm.memcpy.i64
DefaultVisibility
ExternalLinkage - Externally visible.
my_memcpy
Mangled name = my_memcpy
DefaultVisibility
ExternalLinkage - Externally visible.
my_memcpy2
Mangled name =
2009 Jul 18
0
[LLVMdev] Where does llvm.memcpy.i64 and friends get lowered ?
On Jul 18, 2009, at 2:56 PM, Aaron Gray wrote:
> I am iterating through Modules symbols for 'test/CodeGen/X86/memcpy.bc
If you're iterating over functions, just ignore all intrinsics.
-Chris
>
> I get :-
>
> ---------- Functions ----------
> llvm.memcpy.i64
> Mangled name = llvm.memcpy.i64
> DefaultVisibility
> ExternalLinkage -
2015 Jul 21
1
[LLVMdev] RFC: ThinLTO Symbol Linkage and Renaming
Thanks for the comments! Responses below.
Teresa
On Tue, Jul 21, 2015 at 1:06 PM, Duncan P. N. Exon Smith <
dexonsmith at apple.com> wrote:
>
> > On 2015-Jul-14, at 13:33, Teresa Johnson <tejohnson at google.com> wrote:
> >
> > As mentioned in the Updated ThinLTO RFC (
> http://lists.cs.uiuc.edu/pipermail/llvmdev/2015-May/086211.html), I am
> sending the
2009 Jul 18
3
[LLVMdev] Where does llvm.memcpy.i64 and friends get lowered ?
2009/7/18 Chris Lattner <clattner at apple.com>
>
> On Jul 18, 2009, at 2:56 PM, Aaron Gray wrote:
>
> I am iterating through Modules symbols for 'test/CodeGen/X86/memcpy.bc
>
>
> If you're iterating over functions, just ignore all intrinsics.
>
Okay, but it would be nice if the Module object reflected the lowered symbol
names like 'memcpy' too.
2020 Oct 01
3
Creating a global variable for a struct array
>The type you pass to GlobalVariable's constructor for that variable
should be "[10 x %struct.dlist]" because that's what you want storage
for. Then the GlobalVariable itself will be a Constant of type "[10 x
%struct.dlist]*".
Yes, I verified that this is the case.
I enabled assertions and the error seems to occur while creating GlobalVariable for both struct dhash
2019 Feb 22
1
Create the GlobalVariable which have extern in one header file
I have changed it to ExternalLinkage. Now, in LLVM IR, it looks like that:
@DATA_TABLE = external global [0 x i8*], section "data_section", align 16 #0
@DATA_TABLE.1 = global [10 x i8*] [i8* inttoptr (i64 53415718 to i8*), i8* bitcast (void (%class.Hello*)* @_ZN5Hello5ptofnEv to i8*),...], section "data_section", align 16 #0
In my uses:
%arrayidx = getelementptr inbounds [0 x
2015 May 30
2
[LLVMdev] Linking modules across contexts crashes
I get a crash when I try to link multiple modules registered in their
individual contexts.
Documentation for Linker::LinkModules doesn't mention anything about
contexts, and the first link succeeds. But the second link crashes.
Is this not the right way to merge such modules? If not, then what is
the right way?
In any case, documentation for Linker::LinkModules should say if
contexts are
2015 Jul 24
3
[LLVMdev] LLVM linkage flags
An enumeration for the kinds of linkage for global values.
Hi, I'm currently writing a compiler that takes llvm-ir input. I'm a little
confused by the following linkage flags:
Enumerator:
>
> ExternalLinkage: Externally visible function
>
> AvailableExternallyLinkage: Available for inspection, not emission.
>
> LinkOnceAnyLinkage: Keep one copy of function when linking
2015 Jun 08
3
[LLVMdev] Question about usage of LLVMLinkModules()
Hello all,
I am using llvm as a backend to a hobby language I am making. I have
experimented with the C bindings since the project is written in C. I had
no problems building a single lllvm module so far. I am not using a JIT
compiler but at least at the moment am simply generating executables. The
workflow I am using is to build a module with LLVMModuleCreateWithName()
and populate it with the
2004 Jul 02
0
win32-eventlog-0.2.2 released
Hi all,
I''ve released 0.2.2 of win32-eventlog. There was a
rather nasty bug in the read() method I hadn''t noticed
before - it wasn''t reading all the records!
In addition, this package officially requires Ruby
1.8.0 or later, as I have replaced the STR2CSTR()
functions with StringValuePtr().
Let me know if you find any bugs. Thanks.
Dan
2004 Jul 14
0
New allocation framework and other stuff
Hi all,
To be fully "1.8 compliant" I''ve been updating some of
the packages recently as you may have noticed. Mostly
this has been a matter of replacing STR2CSTR() with
StringValuePtr().
I''d also like to start using the new allocation
framework where relevant, too. I didn''t use this for
a long time because we were using 1.6.8 at work, but
that''s
2013 Jun 28
0
[LLVMdev] Problem with linking modules which use a shared type
I've tripped over this behaviour as well. I ended up working around the
problem by creating a new context every time I wanted to link modules
together. Which led to me accidently generating one module using two
different contexts. Which isn't an error that is detected by module
verification. It only causes issues for comparisons like Type equality that
compare pointers, and those types of
2009 Nov 05
2
[LLVMdev] Strange error for libLLVMCore.a
mingw, llvm 2.6 (buid with llvm-gcc)
Example source code:
http://npcontemplation.blogspot.com/2008/06/secret-of-llvm-c-bindings.html
I change
LLVMCreateJITCompiler(&engine, provider, &error);
to
LLVMCreateJITCompiler(&engine, provider, 3, &error);
$ llvm-gcc `llvm-config --cflags` -c fac.c
$ g++ `llvm-config --libs --cflags --ldflags core analysis
executionengine jit
2012 Feb 27
1
[LLVMdev] Where is LLVM-3.0.dll
Anton wrote:
> > I'm trying to use LLVM on Windows for the first time. Keith Sheppard
> > has published some F# bindings:
> >
> > https://github.com/keithshep/llvm-fs
> Keith specified the build instructions there, what were the problems of using
> them?
I followed both those instructions and (separately) the instructions from the LLVM "Getting Started with
2013 Jun 27
2
[LLVMdev] Problem with linking modules which use a shared type
Hi,
I stumbled upon a strange thing regarding types and module linking, which I don't quite get, so maybe someone around here can enlighten me.
Consider the following code, which will create 2 modules m1 and m2, and a named structured type %T = { i32 }; m1 contains only a function definition f(%T), m2 contains a function declaration f(%T) and a function definition h(%T), where h will call f