search for: bugpoint

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 be...

...estcases, since I do not see a clear resolution for them. In a lot of cases disabling or fixing a warning might be enough, but since I can't always see what a test is supposed to test, I'm afraid that that will actually render the testcase useless. Of these final 20 tests, 3 are related to bugpoint producing stderr output (but I can't see if that is expected output or not). Two are related to an invalid -mcpu option, I think the corresponding RUN lines should be removed or changed? One is related to the -mattr=sse1 option that is not supported (anymore?). The remaining 14 are warnings pro...

On Mar 26, 2014, at 6:56 PM, Krzysztof Parzyszek <kparzysz at codeaurora.org> wrote: > On 3/26/2014 11:39 AM, İsmail Dönmez wrote: >> >> make check-all but yes make check would suffice. Thanks! > > I see two reported failures: > > > FAIL: LLVM :: BugPoint/compile-custom.ll (459 of 9992) > ******************** TEST 'LLVM :: BugPoint/compile-custom.ll' FAILED ******************** > Script: > -- > /usr/home/kparzysz/bld.lv/Release+Asserts/bin/bugpoint -load /usr/home/kparzysz/bld.lv/Release+Asserts/lib/BugpointPasses.so --compile-cu...

...lit/lit.py --param build_config=. --param build_mode=Release -sv --param llvm_site_config=/home/steve/llvm-build/test/lit.site.cfg --param llvm_unit_site_config=/home/steve/llvm-build/test/Unit/lit.site.cfg /home/steve/llvm-build/tes t -- Testing: 6378 tests, 4 threads -- Testing: 0 FAIL: LLVM :: BugPoint/metadata.ll (351 of 6378) ******************** TEST 'LLVM :: BugPoint/metadata.ll' FAILED ******************** Script: -- /home/steve/llvm-build/bin/./bugpoint -load /home/steve/llvm-build/lib/./BugpointPasses.so /usr/home/steve/llvm/test/BugPoint/metadata.ll -output-prefix /usr/ho me/steve...

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': bugpoint-test-program.bc.cbe.c:5...

I've made quite a bit of progress getting bugpoint to work with our (non-gcc) tools. In fact I caught the alignment bug I recently posted about using it. But it's not there yet. In particular, I am seeing this scenario a lot (comments in brackets): *** Found miscompiling pass: -instcombine Emitted bitcode to 'bugpoint-passinput.bc'...

Hi everyone, I want to test the passes in llvm, and I got some passes sequences that caused the crash of opt. Although I can use bugpoint to narrow down the source of problems, I can only get some reduced and simplified IR and passes to reproduce the problem. My question is how to get the reduced IR of the original IR file to reproduce the problem. For example, "opt a.bc -a -b -c -d (where a, b, c and d are passes)" has a...

Hi, I am trying to reduce what I believe to be a miscompilation bug. Running lli on my bitcode file causes a segmentation fault. However, running bugpoint as bugpoint file.bc gives me the following errors, /tmp/ccAdmNqH.o: In function `_ZL17bus_error_handleriP7siginfoPv': bugpoint-test-program.bc-Vega5s.cbe.c:(.text+0x1b4e1): undefined reference to `std::cerr' /tmp/ccAdmNqH.o: In function `bb_poolcheck_debug': bugpoint-test-program.bc-V...

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 `memcpy' > bugpoint-test-program.bc.cbe.c: In function `main':...

--- tools/bugpoint/bugpoint.cpp | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) I came across this while 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/bugp...

..." 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 $ PATH=$HOME/path/to/my/llvm/build/bin:$PATH bugpoint -compile-custom -compile-command ./run_llc.sh test.ll - Matthias > On Jul 31, 2018, at 11:03 AM, Friedman, Eli via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On 7/31/2018 10:10 AM, David Greene via llvm-dev wrote: >> I have a failing test and bugpoint would be the per...

...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 cs.uiuc.edu> > >Seung Jae Lee wrote: >> Hello. >> Can I use debugging options such as 'step', 'next'(in gdb) also in LLVM bugpoint? >> >I assume you're asking if you can use commands lik...

I have a failing test and bugpoint would be the perfect tool to help narrow it down. llc is the failing tool. It fails with one set of options and passes with another. I was hoping to use bugpoint like this: bugpoint -safe-llc -run-llc <testcase> -tool-args <failing args> -safe-tool-args <passing args> Unfortu...

> bugpoint should be a standalone tool. It should not require a separate > script to handle remote execution. Why is the script needed? Bugpoint is a standalone too and does not require any separate script. The script is a helper for using ssh as a remote client. Bugpoint should not be aware of any detai...

...obal address: stdout > >> > >> This error means you're generating a reference to a symbol named > >> stdout, which does not exist on OS X. Why do you think this is a bug > >> in lli? > > > > Eli, > > What about the output that I see from bugpoint... > > > > http://llvm.org/bugs/show_bug.cgi?id=14142#c4 > > > > which seems to suggest that the actual problem is an alignment issue. > > > > ugpoint-test-program.bc.llc.s.gcc.exe -lm -O2 > > bugpoint-test-program.bc:4:Alignment too large: 15. assumed. &gt...

On Jul 8, 2009, at 1:52 PM, Viktor Kutuzov wrote: >> bugpoint should be a standalone tool. It should not require a >> separate >> script to handle remote execution. Why is the script needed? > > Bugpoint is a standalone too and does not require any separate script. > The script is a helper for using ssh as a remote client. Ok. > &g...

Hello Evan, Thanks for looking at the patch. > This should use std::cerr and make sure it is wrapped inside the DEBUG > macro. Will do. > Also, we don't want RemoteRunSafely.sh to be under utils/bugpoint. > Can you move it to test-suite? Are you planning to change the llvm > test suite makefile to make use of RemoteRunSafely.sh? I thought about bugpoint remote mode and the RemoteRunSafely.sh script more as a manual tool rather than a part of the test suit. Unless I'm missing somethi...

...config=. --param build_mode=Release -sv --param > llvm_site_config=/home/steve/llvm-build/test/lit.site.cfg --param llvm_unit_site_config=/home/steve/llvm-build/test/Unit/lit.site.cfg /home/steve/llvm-build/tes > t > -- Testing: 6378 tests, 4 threads -- > Testing: 0 > FAIL: LLVM :: BugPoint/metadata.ll (351 of 6378) > ******************** TEST 'LLVM :: BugPoint/metadata.ll' FAILED ******************** > Script: > -- > /home/steve/llvm-build/bin/./bugpoint -load /home/steve/llvm-build/lib/./BugpointPasses.so /usr/home/steve/llvm/test/BugPoint/metadata.ll -output-pre...

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 generator to test for a crash: <llc...

Hi, I didn't get a clear idea what to do whit this problem: OptimizerDriver.cpp seems to be unix platform specific. However, I'm compiling this on MinGW. Shouldn't this be moved to lib/System/<platform>? Any suggestions? -------------------------- c:/Projects/src/llvm/tools/bugpoint/OptimizerDriver.cpp:28:22: sys/wait.h: No such file or directory c:/Projects/src/llvm/tools/bugpoint/OptimizerDriver.cpp: In member function ` bool llvm::BugDriver::runPasses(const std::vector<const llvm::PassInfo*, std::allocator<const llvm::PassInfo*> >&, std::string&,...