search for: llvm_shutdown_obj

Chris, I'm using a llvm_shutdown_obj object and it calls llvm_shutdown when I delete it. Do I need to call llvm_shutdown() again afterwards? It looks to me like the static object is being created after my program exits main(). From: Chris Lattner [mailto:clattner at apple.com] Sent: Friday, January 13, 2012 10:11 AM To: Villmow, Mica...

...) we've got some frontend which generates LLVM IR. Now I'm observing strange *llvm_shutdown* behavior. If I called it when I was done using the LLVM APIs I saw that destructors of static objects created new ManagedStatic objects, which was never freed. Then I tried to use static global llvm_shutdown_obj to cause destruction of ManagedStatics after calling all static destructors. In that case I got "pure virtual function call" because of early release of BumpPtrAllocator::DefaultSlabAllocator. Call stack for this case: msvcr100d.dll!_purecall() Line 54 + 0x7 bytes C > ll...

...isabled, which is the case for llvm-link. To enable @file support in llvm-link, a small change is needed: --- llvm-link.cpp.orig 2012-09-20 16:10:50.000000000 -0400 +++ llvm-link.cpp 2012-09-20 16:11:24.000000000 -0400 @@ -83,7 +83,7 @@ LLVMContext &Context = getGlobalContext(); llvm_shutdown_obj Y; // Call llvm_shutdown() on exit. - cl::ParseCommandLineOptions(argc, argv, "llvm linker\n"); + cl::ParseCommandLineOptions(argc, argv, "llvm linker\n", true); unsigned BaseArg = 0; std::string ErrorMessage; Sam -----Original Message----- From: Liu, Yaxun (Sam) Se...

Oh, you probably also need to create a static llvm_shutdown_obj. On 06/01/2011 02:19 PM, Michael Ilseman wrote: > Thanks for the reply! Unfortunately, that seems to have the same > effect as setting llvm::TimePassesIsEnabled myself, and all my same > problems still apply as the TimingInfo's destructor (PassManager.cpp) > is still never called....

...> > To enable @file support in llvm-link, a small change is needed: > > --- llvm-link.cpp.orig 2012-09-20 16:10:50.000000000 -0400 > +++ llvm-link.cpp 2012-09-20 16:11:24.000000000 -0400 > @@ -83,7 +83,7 @@ > > LLVMContext &Context = getGlobalContext(); > llvm_shutdown_obj Y; // Call llvm_shutdown() on exit. > - cl::ParseCommandLineOptions(argc, argv, "llvm linker\n"); > + cl::ParseCommandLineOptions(argc, argv, "llvm linker\n", true); > > unsigned BaseArg = 0; > std::string ErrorMessage; > > Sam > > -----Origin...

Thanks for the reply! Unfortunately, that seems to have the same effect as setting llvm::TimePassesIsEnabled myself, and all my same problems still apply as the TimingInfo's destructor (PassManager.cpp) is still never called. Running it in the debugger shows that TimerGroup's removeTimer method is never called, nor is it's destructor (but it's constructor is). On Wed, Jun 1, 2011

...e running bugpoint --help, hope you don't mind the git patch output :) diff --git a/tools/bugpoint/bugpoint.cpp b/tools/bugpoint/bugpoint.cpp index 2364675..587077e 100644 --- a/tools/bugpoint/bugpoint.cpp +++ b/tools/bugpoint/bugpoint.cpp @@ -67,7 +67,7 @@ int main(int argc, char **argv) { llvm_shutdown_obj X; // Call llvm_shutdown() on exit. cl::ParseCommandLineOptions(argc, argv, "LLVM automatic testcase reducer. See\nhttp://" - "llvm.org/docs/CommandGuide/bugpoint.html" + "llvm.org/...

On Jan 13, 2012, at 10:08 AM, Villmow, Micah wrote: > > Are these known issues? If so, how do I free this memory? > Hi Micah, Please try calling llvm_shutdown() -Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120113/a51dc89c/attachment.html>

...bitcode file> Micah From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Villmow, Micah Sent: Friday, January 13, 2012 10:23 AM To: Chris Lattner Cc: LLVM Developers Mailing List Subject: Re: [LLVMdev] Memory leaks in LLVM on linux Chris, I'm using a llvm_shutdown_obj object and it calls llvm_shutdown when I delete it. Do I need to call llvm_shutdown() again afterwards? It looks to me like the static object is being created after my program exits main(). From: Chris Lattner [mailto:clattner at apple.com] Sent: Friday, January 13, 2012 10:11 AM To: Villmow, Mica...

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>()

...> > To enable @file support in llvm-link, a small change is needed: > > --- llvm-link.cpp.orig 2012-09-20 16:10:50.000000000 -0400 > +++ llvm-link.cpp 2012-09-20 16:11:24.000000000 -0400 > @@ -83,7 +83,7 @@ > > LLVMContext &Context = getGlobalContext(); > llvm_shutdown_obj Y; // Call llvm_shutdown() on exit. > - cl::ParseCommandLineOptions(argc, argv, "llvm linker\n"); > + cl::ParseCommandLineOptions(argc, argv, "llvm linker\n", true); > > unsigned BaseArg = 0; > std::string ErrorMessage; > > Sam > > -----Origin...

Liu, Yaxun (Sam) wrote: > I am proposing to add an option to llvm-link allow it to get a list of > input bitcode file names from a file. > > The reason is that there is a limitation for command line length which > limits the number of input bitcode files that can be passed to > llvm-link. By adding this option we can bypass such limitation. > > The name of the option can be

I am proposing to add an option to llvm-link allow it to get a list of input bitcode file names from a file. The reason is that there is a limitation for command line length which limits the number of input bitcode files that can be passed to llvm-link. By adding this option we can bypass such limitation. The name of the option can be discussed. My initial proposal would be -input-file-list.

Patch for review. On Mon, Aug 21, 2017 at 11:45 PM Puyan Lotfi <puyan.lotfi.llvm at gmail.com> wrote: > Ping. > > Still working on preparing code for review. Will have a patch for review > ready in the coming days. > > PL > > On Tue, Aug 15, 2017 at 12:06 PM Puyan Lotfi <puyan.lotfi.llvm at gmail.com> > wrote: > >> Hi, >> >> >>

...lvm::GlobalVariable' /projects/compiler/llvm-gcc/gcc/llvm-internal.h:46: error: forward declaration of `struct llvm::GlobalVariable' /projects/compiler/llvm-gcc/gcc/llvm-backend.cpp: In function `void llvm_asm_file_end()': /projects/compiler/llvm-gcc/gcc/llvm-backend.cpp:435: error: `llvm_shutdown_obj' was not declared in this scope /projects/compiler/llvm-gcc/gcc/llvm-backend.cpp:435: error: expected `;' before `X' /projects/compiler/llvm-gcc/gcc/llvm-backend.cpp:451: error: `PointerType' has not been declared /projects/compiler/llvm-gcc/gcc/llvm-backend.cpp:451: error: incomp...