Displaying 20 results from an estimated 6000 matches similar to: "[LLVMdev] Possible Bad Assertion in Value.cpp"
2008 Feb 15
0
[LLVMdev] Possible Bad Assertion in Value.cpp
On Feb 15, 2008, at 1:57 PM, John Criswell wrote:
> Dear All,
>
> I'm getting the following assertion from a program I've written:
>
> /home/vadve/criswell/src/llvm22/lib/VMCore/Value.cpp:57: virtual
> llvm::Value::~Value(): Assertion `use_empty() && "Uses remain when a
> value is destroyed!"' failed.
>
> This occurs when I free a Module
2008 Feb 15
2
[LLVMdev] Possible Bad Assertion in Value.cpp
Chris Lattner wrote:
> On Feb 15, 2008, at 1:57 PM, John Criswell wrote:
>
>
>> Dear All,
>>
>> I'm getting the following assertion from a program I've written:
>>
>> /home/vadve/criswell/src/llvm22/lib/VMCore/Value.cpp:57: virtual
>> llvm::Value::~Value(): Assertion `use_empty() && "Uses remain when a
>> value is
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 25
2
[LLVMdev] PLEASE help with Alias Analysis initialization assertion at the end of my pass
Hello all,
I really, really, really need your help. This is my third email now,
please don't ignore me! I understand this must be a trivial thing, but
I've ground to a halt, and REALLY need some guidance. Please see below for
the context of my problem. I'm not trying to be a waste of time, but I'm
desperate here.
I have a getAnalysisUsage method which does the following
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 25
0
[LLVMdev] PLEASE help with Alias Analysis initialization assertion at the end of my pass
Griffin Wright wrote:
>
> Hello all,
>
> I really, really, really need your help. This is my third email now,
> please don't ignore me! I understand this must be a trivial thing, but
> I've ground to a halt, and REALLY need some guidance. Please see below for
> the context of my problem. I'm not trying to be a waste of time, but I'm
> desperate here.
2012 Jan 25
1
[LLVMdev] PLEASE help with Alias Analysis initialization assertion at the end of my pass
Yes, it is a pass.
Here is a very general overview of the file structure as far as the AA is
concerned. LLVM is not my strong-suit, I do hardware simulators, not
compilers.
using namespace llvm;
char RelRecovery::ID = 0;
static RegisterPass<RelRecovery> X("relRecovery",
"Reliability transformation for lightweight recovery");
void
2012 Jan 23
1
[LLVMdev] Assertion `AA && "AA didn't call InitializeAliasAnalysis in its run method!"' failed.
Hello all,
I am working with someone else's LLVM code, which is about 8 months old.
Part of this pass involves AliasAnalysis, and I'm getting the above
assertion when the pass completes.
The dump is as follows:
--------------------------------
Program received signal SIGABRT, Aborted.
0xf7fdf430 in __kernel_vsyscall ()
(gdb) bt
#0 0xf7fdf430 in __kernel_vsyscall ()
#1 0xf602e921 in
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 %'
2007 Dec 03
1
[LLVMdev] Using Function Passes from Module Passes
Dear All,
I'm having some problems using a function pass from a Module pass. My
code is as follows:
DominatorTree & domTree;
...
Function &F = *I; // I is an interator from using Module::begin()
...
domTree = getAnalysis<DominatorTree>(F);
When I compile this code, I get the following error:
/home/vadve/criswell/src/llvm22/include/llvm/Pass.h: In member function
2009 Mar 12
2
[LLVMdev] Suggestion: include object data in assertion messages
Hi all,
There are many assertions sprinkled throughout the llvm codebase,
which is a GoodThing. Most of the assertions even have informative
messages, which is a BetterThing.
However, assertion messages are static strings, and don't include any
information about the particular object/value which caused the
assertion. In a 'data oriented' system like llvm, this makes it really
2017 Jan 23
5
Upcoming removal of std::auto_ptr (in C++1z)
The upcoming C++1z (probably C++17) standard will not contain several
things - most notably auto_ptr.
Soon, libc++ will not be providing auto_ptr by default when building in
C++1z mode.
You'll be able to get it back with a
"-D_LIBCPP_ENABLE_CXX17_REMOVED_AUTO_PTR" on your command line, or "#define
_LIBCPP_ENABLE_CXX17_REMOVED_AUTO_PTR" before including any libc++ header
2009 Mar 12
0
[LLVMdev] Suggestion: include object data in assertion messages
On Mar 12, 2009, at 1:47 AM, someguy wrote:
> However, assertion messages are static strings, and don't include any
> information about the particular object/value which caused the
> assertion. In a 'data oriented' system like llvm, this makes it really
> difficult to pinpoint which node is actually triggering the assertion.
>
> For example, in
2008 Apr 07
2
[LLVMdev] Problem Linking Analysis Group
Dear All,
I'm having the following problem linking code that defines and uses an
AnalysisGroup.
I have an analysis group defined as follows:
class PoolAllocateGroup {
public:
static char ID;
virtual ~PoolAllocateGroup ();
virtual PA::FuncInfo *getFuncInfo(Function &F);
...
};
... which is then inherited by a ModulePass:
class PoolAllocate : public ModulePass , public
2009 Apr 14
3
[LLVMdev] SVN Head Error Building on Mac OS X
Dear All,
Has anyone else noticed the following problem building LLVM on Mac OS X:
find-cycles.pl: Circular dependency between *.a files:
find-cycles.pl: libLLVMAsmPrinter.a libLLVMCodeGen.a libLLVMSelectionDAG.a
llvm[1]: Building llvm-config script.
cat: /Users/criswell/box/x86/llvm22/tools/llvm-config/FinalLibDeps.txt:
No such file or directory
-- John T.
2013 Sep 18
1
[LLVMdev] In llvm, how can I delete a whole branch elegantly?
Hi,
I am trying to prune some uninteresting llvm ir branches, corresponding
to the *if-else* condition in the source code. And here is the procedures:
1. Get the BasicBlock containing the BranchInst which has 2
successors(in order to keep consistent with the source code I am using the
llvm ir without any optimizations, so SelectInst/SwitchInst/PHINode is
absent), one of which should be
2007 Dec 18
2
[LLVMdev] Another Pass Manager Assertion
Dear All,
The attached code (which is a contrived test case) hits the following
assertion:
test:
/home/vadve/criswell/src/llvm22/include/llvm/PassAnalysisSupport.h:226:
AnalysisType& llvm::Pass::getAnalysisID(const llvm::PassInfo*,
llvm::Function&) [with AnalysisType = Pass1]: Assertion `ResultPass &&
"getAnalysis*() called on an analysis that was not "
2009 Apr 14
0
[LLVMdev] SVN Head Error Building on Mac OS X
John Criswell wrote:
> Dear All,
>
> Has anyone else noticed the following problem building LLVM on Mac OS X:
>
> find-cycles.pl: Circular dependency between *.a files:
> find-cycles.pl: libLLVMAsmPrinter.a libLLVMCodeGen.a libLLVMSelectionDAG.a
> llvm[1]: Building llvm-config script.
> cat: /Users/criswell/box/x86/llvm22/tools/llvm-config/FinalLibDeps.txt:
> No such
2008 Feb 15
0
[LLVMdev] Possible Bad Assertion in Value.cpp
>> You probably have an instruction that you removed from the module but
>> didn't delete. The module dtor works fine: it uses
>> 'dropAllReferences' to clear the operands of instructions before
>> deleting the instructions themselves.
>>
> Okay. I wasn't aware I had to delete unneeded values as well as
> remove
> them. I'll try that.