Displaying 20 results from an estimated 500 matches similar to: "[LLVMdev] Interpreter Destructor"
2009 Jul 01
0
[LLVMdev] Interpreter Destructor
On Jul 1, 2009, at 8:28 AM, David Bertouille wrote:
> Would it not be better to clear the Functions
> map in the Interpreter desctructor since it data in it may no longer
> be
> valid?
Probably. Patches welcome!
--Owen
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2620 bytes
Desc: not
2009 Jun 30
2
[LLVMdev] JIT on Windows x64
Hi,
I'm new to LLVM and have some questions about using the JIT on Windows
x64. I am aware that this is currently broken but am attempting to use
the hack/patch proposed in this bug
http://llvm.org/bugs/show_bug.cgi?id=3739.
I checked out the revision the patch was created for (66183) and applied
it but the assembler generated seems to fail whenever it reaches a
movaps insctruction.
2005 May 08
1
ruby destructor hooks
Hi
Is there a way of finding out when or whether the wx object referenced
in ruby is still alive?
Here''s my problem
# register that +wx_control+ should update on application events of type
+event_type+
def add_subscriber(wx_control, app_event_type)
@subscriptions[app_event_type].push(wx_control)
end
# later
def broadcast(app_event)
@subscriptions[app_event.type].each { |
2007 Aug 10
0
kde-window-decorator crash in destructor
Hi,
After getting a bug report in Debian [1] about kde-window-decorator
crashing in some destructors, I found several other similar reports in
Ubuntu [2], KDE [3] (marked as invalid) and also on this mailing list
several months ago [4] without any interesting reply. The backtrace is
available in all these bugs, especially in [1].
I was about to open a bug at bugzilla.freedesktop.org but first:
*
2014 Jun 17
1
[PATCH] drm/nouveau: fix oops in display destructor with headless cards
If init doesn't run then disp->outp might not be initialized, resulting in an oops.
Signed-off-by: Maarten Lankhorst <maarten.lankhorst at canonical.com>
---
diff --git a/drivers/gpu/drm/nouveau/core/engine/disp/base.c b/drivers/gpu/drm/nouveau/core/engine/disp/base.c
index c41f656abe64..9c38c5e40500 100644
--- a/drivers/gpu/drm/nouveau/core/engine/disp/base.c
+++
2012 May 24
1
[LLVMdev] JITEventListener destructor location
Hello,
I've recently finished moving a cross-platform project to LLVM 3.0 and now transitioning to 3.1. One of the things I've hit is on OS X, I have linker errors involving JITEventListener and I've noticed if I move the JITEventListener destructor out of JIT.cpp and into JITEventListener.h (like other functions of JITEventListener), the linker is much happier. I'd like to push
2009 Jul 21
2
destructor for S4 class objects in analogy to C++
Hi all,
I'm wondering if there is a way to define a destructor function (to free
memory) for S4 class objects in analogy to C++?
rm() combined with gc() does not seem to be a good idea (Chambers, 2008).
So could it be done on the C/C++ level or is it even already available in
the "internals"?
Many thanks,
David
[[alternative HTML version deleted]]
2013 Aug 20
0
sf bug 256 - Virtual functions in destructor
In 2007, user reported a segfault in
FLAC::Encoder::File::progress_callback() when called from ~Stream().
Original report at https://sourceforge.net/p/flac/bugs/256/
Hello! Sorry, english is not my best language.
I use libFLAC++ API. I have some problems. In libFLAC API all OK.
Unhandled exception at 0x00000000 in Test.exe: 0xC0000005: Access
violation reading location 0x00000000.
Call stack
2011 Oct 16
0
[LLVMdev] Static destructor problem with recent HEAD
On Sat, Oct 15, 2011 at 9:20 PM, Talin <viridia at gmail.com> wrote:
> I recently updated my version of LLVM from revision 140108 to 142082, and
> several things broke, most of which were easily fixed. However, I'm now
> getting a "pure virtual method called" exception (__cxa_pure_virtual) which
> I wasn't getting before. This is happening in the destructor of
2005 Jan 07
1
Destructor for S4 objects?
Hi,
To write a "constructor" for an S4 object, you make an initialize method
which will be called by new. But how would I make a "destructor" method to
be called when the S4 object is garbage collected? I'm looking at
reg.finalizer, but I'm not sure how to make that work for an S4 object.
I want to write a destructor because my S4 object's initialize method
2011 Oct 16
2
[LLVMdev] Static destructor problem with recent HEAD
I recently updated my version of LLVM from revision 140108 to 142082, and
several things broke, most of which were easily fixed. However, I'm now
getting a "pure virtual method called" exception (__cxa_pure_virtual) which
I wasn't getting before. This is happening in the destructor of a
statically-initialized object. (More precisely, it's blowing up in a
BumpPtrAllocator,
2012 Sep 21
0
[LLVMdev] Clang API parsing of the destructor
On Fri, Sep 21, 2012 at 12:22 PM, Kamaljit Lall <klall at factset.com> wrote:
> I am using the clang API (version 3.1 - trunk 153913) to compile some
> very simple code as follows****
>
> class MyClass
> {
> ~MyClass() ;
>
> };
>
> MyClass::~MyClass()
> {
>
> }
>
> int main()
> {
> return 0;
> } ****
>
> My problem is that
2010 Aug 27
3
[PATCH 0 of 3] libxl: cleanups for type destructor generation
Following series cleans up a few niggles in the libxl destructor
autogeneration.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
2012 Sep 21
2
[LLVMdev] Clang API parsing of the destructor
I am using the clang API (version 3.1 - trunk 153913) to compile some very simple code as follows
class MyClass
{
~MyClass() ;
};
MyClass::~MyClass()
{
}
int main()
{
return 0;
}
My problem is that I get the error message: test.cpp:20:10: error: destructor cannot have a return type MyClass::~MyClass()
If someone can point me to the right direction that would be great. It compiles fine if
2011 Oct 16
0
[LLVMdev] Static destructor problem with recent HEAD
Interestingly, I also get a similar error in a different executable (my
unittest):
pure virtual method called
terminate called without an active exception
0 tartc 0x00000001010a8265 PrintStackTrace(void*) + 53
1 tartc 0x00000001010a88cc SignalHandler(int) + 364
2 libSystem.B.dylib 0x00007fff831341ba _sigtramp + 26
3 libSystem.B.dylib 0x7261742e65637365 _sigtramp +
2018 May 11
0
About Error: Interpreter has not been linked in
Ok. I figured out. Following methods needs to be called. That fixed the
issue.
llvm::InitializeNativeTarget();
LLVMInitializeNativeAsmPrinter();
LLVMInitializeNativeAsmParser();
LLVMLinkInMCJIT();
Aaron
On Thu, May 10, 2018 at 8:33 PM, Aaron <acraft at gmail.com> wrote:
> Hello,
>
> When I try to create execution engine I do get "*Interpreter has not been
> linked
2012 Jan 13
2
[LLVMdev] Memory leaks in LLVM on linux
I am trying to figure out how to free up some memory that seems to be lost when running valgrind under our internal application. The stack traces I get are:
==19966== 4 bytes in 1 blocks are still reachable in loss record 1 of 12
==19966== at 0x402569A: operator new(unsigned int) (vg_replace_malloc.c:255)
==19966== by 0x5D9BBE8: void* llvm::object_creator<llvm::PassRegistry>()
2009 May 13
0
[LLVMdev] LLVM is deleting an array pointer without using array notation
Here is the warning I am getting:
PseudoSourceValue.cpp
R:\SDKs\llvm\trunk\include\llvm/Support/ManagedStatic.h(23) : warning
C4156: deletion of an array expression without using the array form of
'delete'; array form substituted
R:\SDKs\llvm\trunk\include\llvm/Support/ManagedStatic.h(72) :
see reference to function template instantiation 'void
2018 May 11
1
About Error: Interpreter has not been linked in
I believe the correct way is actually include the Interpreter’s header and the rest is handled automatically. Should be similar for MCJIT
Zhang
> On 11 May 2018, at 05:21, Aaron via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>
> Ok. I figured out. Following methods needs to be called. That fixed the issue.
>
> llvm::InitializeNativeTarget();
>
2011 Oct 16
2
[LLVMdev] Static destructor problem with recent HEAD
On Sat, Oct 15, 2011 at 9:49 PM, Chandler Carruth <chandlerc at google.com>wrote:
> On Sat, Oct 15, 2011 at 9:20 PM, Talin <viridia at gmail.com> wrote:
>
>> I recently updated my version of LLVM from revision 140108 to 142082, and
>> several things broke, most of which were easily fixed. However, I'm now
>> getting a "pure virtual method called"