similar to: bugpoint --tool-args and --safe-tool-args

This is what works for me, when I want to reduce an llc failure triggering a failure with a "foo bar baz" in the assert message (the grep for the error message avoids reducing to an unrelated failure): $ cat run_llc.sh #!/bin/sh if ! $HOME/dev/llvm/build/bin/llc "$@" 2>&1 | grep "foo bar baz"; then exit 0 else exit $? fi $

> -----Original Message----- > From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of Justin > Bogner via llvm-dev > Sent: Monday, July 22, 2019 11:44 > To: Jay Foad via llvm-dev <llvm-dev at lists.llvm.org> > Subject: Re: [llvm-dev] Fwd: bugpoint can't automatically select a safe > interpreter! > > Bugpoint's user interface is notoriously

I'm having some trouble using bugpoint with newer version of gcc (bugpoint debug output below). I looked into the "conflicting type for malloc" problem and it doesn't seem easy to solve due to the unknown size of size_t (see LowerAllocations.cpp). The "void main()" problem is probably a result of this test being converted from Fortran. I'll have to dig into

On Wednesday 16 July 2008 10:31, David Greene wrote: > On Wednesday 16 July 2008 10:12, David Greene wrote: > > I'm having some trouble using bugpoint with newer version of gcc > > (bugpoint debug output below). > > I was using gcc 4.1.2. When I try 3.2.3 I get: > > bugpoint-test-program.bc.cbe.c:237: warning: conflicting types for built-in > function

I tried to reduce the test case in https://bugs.llvm.org/show_bug.cgi?id=42706. Here it is crashing opt: $ ~/llvm-debug/bin/opt -use-gpu-divergence-analysis -divergence stripped.ll WARNING: You're attempting to print out a bitcode file. This is inadvisable as it may cause display problems. If you REALLY want to taste LLVM bitcode first-hand, you can force output with the `-f' option.

On Wednesday 16 July 2008 10:12, David Greene wrote: > I'm having some trouble using bugpoint with newer version of gcc (bugpoint > debug output below). I was using gcc 4.1.2. When I try 3.2.3 I get: bugpoint-test-program.bc.cbe.c:237: warning: conflicting types for built-in function `memcpy' bugpoint-test-program.bc.cbe.c: In function `main':

----- Original Message ----- > From: "Reed Kotler" <rkotler at mips.com> > To: "Hal Finkel" <hfinkel at anl.gov> > Cc: LLVMdev at cs.uiuc.edu > Sent: Friday, November 22, 2013 11:18:53 PM > Subject: Re: bugpoint question > > In that case it tries to do something but fails. > > rkotler at ubuntu-rkotler:~/testmips16$ >

Hi,all I ran my generated whole-program bitcode file which performs as a bodytrack tool, it can give me the right result but with a stack dump before it exsits Update Error : Model observation failed for time : 1 Error loading observation data terminate called after throwing an instance of 'std::bad_cast' what(): std::bad_cast 0 lli 0x08b713d2 1 lli 0x08b71247

In that case it tries to do something but fails. rkotler at ubuntu-rkotler:~/testmips16$ /home/rkotler/llvmw/install/bin/bugpoint casts.bc -llc-safe --safe-tool-args -target=mips-linux-gnu -mcpu=mips16 -mips16-constant-islands Read input file : 'casts.bc' *** All input ok Initializing execution environment: Found llc: /home/rkotler/llvmw/install/bin/llc Running the code

I would like to use bugpoint to debug some of my passes. I have read the documentation, but I don't completely understand it. I have a bitcode file X.bc that I transform using the following commands: opt -mypass1 -f -o X.1.bc X.bc // transform with mypass1 llvm-link -f -o X.2.bc X.1.bc support.bc // link with support.bc opt -mypass2 -f -o X.3.bc X.2.bc // transform with mypass2 After

----- Original Message ----- > From: "reed kotler" <rkotler at mips.com> > To: LLVMdev at cs.uiuc.edu > Sent: Friday, November 22, 2013 8:40:24 PM > Subject: [LLVMdev] bugpoint question > > This is my first time using bugpoint. I'm getting the following > error: > > /home/rkotler/llvmw/install/bin/bugpoint -run-llc casts.bc > --tool-args >

Thank you so much for this info. That's exactly what I want. But, I'm still not sure about using -g. Let me imagine I am modifying x86 assembly instructions and trying to test it with 'hello.c' to check out the assembly is properly emitted. I should type "$ llvm-gcc hello.c -o hello" to have the bytecode of 'hello.c'. And then I can have an x86 assembly mnemonics

Thank you for this information. If so, is there any way to grasp which kinda data throw in and out in LLVM as shown in such a way in gdb? Thanks, Seung Jae Lee ---- Original message ---- >Date: Tue, 20 Feb 2007 23:54:04 -0600 >From: "John T. Criswell" <criswell at cs.uiuc.edu> >Subject: Re: [LLVMdev] bugpoint usage >To: LLVM Developers Mailing List <llvmdev at

Hi Nan Zhu, > I use Bugpoint to check it , Bugpoint gives me the following information: > > > Read input file : 'bodytrack.bc' > *** All input ok > Initializing execution environment: Found gcc: /usr/lib/ccache/gcc > Running the code generator to test for a crash: <cbe>*** Debugging code > generator crash! > > Error running tool: >

On Dec 6, 2010, at 2:18 AM, Ryan M. Lefever wrote: > > llc X.3.bc arg1 arg2 > > That llc command is currently seg faulting because of a bug in one of my > passes or in support.bc. Can I use bugpoint to find a smaller version of > X.bc that produces the same problem? Specifically how would I call > bugpoint to do that? bugpoint X.3.bc -run-llc -tool-args arg1 arg2 /jakob

This is my first time using bugpoint. I'm getting the following error: /home/rkotler/llvmw/install/bin/bugpoint -run-llc casts.bc --tool-args -target mips-linux-gnu -mcpu=mips16 -mips16-constant-islands Read input file : 'casts.bc' *** All input ok Initializing execution environment: Found llc: /home/rkotler/llvmw/install/bin/llc Sorry, I can't automatically select a

Hi, I have a program that runs when statically compiled using llc and gcc but crashes with a segmentation fault when run with lli. I am trying to debug it with bugpoint and the initial part of bugpoint seems to be suggesting that I am somehow missing the linking with the libraries having dlsym/dlopen although I am passing it to lli : *$ bugpoint -run-jit

Hey folks, I am not sure who owns bugpoint, but twice now we have had to apply this patch manual. I don’t have commit access, so, help submitting this would be awesome. -------------- next part -------------- A non-text attachment was scrubbed... Name: bugpoint.git.patch Type: application/octet-stream Size: 507 bytes Desc: not available URL:

On Tue, May 23, 2017 at 2:40 PM Reid Kleckner <rnk at google.com> wrote: > We have the LLVM_DISABLE_CRASH_REPORT environment variable, but that's > more about whether we should do crash reporting or not. > > It would be pretty reasonable to have another one to disable all this > stuff. It would also be reasonable to have a cmake option that compiles > this stuff away,

Do something like this: bugpoint -run-llc <bitcode file> --tool-args -- <llc arguments> Cameron On May 23, 2011, at 1:33 PM, Arushi Aggarwal wrote: > Hi, > > What is the best way to debug an llc crash using bugpoint? > > I am getting the following crash that I would like to reduce > > llc: /home/vadve/aggarwa4/llvm29/llvm-2.9/lib/MC/MCAsmStreamer.cpp:273: