Displaying 20 results from an estimated 4000 matches similar to: "bugpoint, LLVM tools (opt, llc, etc), and symbolizing costs"
2017 May 24
1
bugpoint, LLVM tools (opt, llc, etc), and symbolizing costs
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,
2008 Jul 16
0
[LLVMdev] bugpoint / cbe Problems
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':
2008 Jul 16
2
[LLVMdev] bugpoint / cbe Problems
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
2011 May 03
1
[LLVMdev] Using Bugpoint to debug miscompilation
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
2007 Feb 21
2
[LLVMdev] bugpoint usage
Hello.
Can I use debugging options such as 'step', 'next'(in gdb) also in LLVM bugpoint?
Thank you.
2018 Jul 31
2
bugpoint --tool-args and --safe-tool-args
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>
Unfortunately, this doesn't seem to be possible. According to the
2010 Dec 06
3
[LLVMdev] using bugpoint
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
2012 Aug 21
2
[LLVMdev] bugpoint (and possibly others) need to be compiled with -rdynamic
While running the llvm tests, I get several error messages like these:
[1/1] Running the LLVM regression tests
FAILED: cd /home/steve/llvm-build/test && /usr/local/bin/python /home/steve/llvm/utils/lit/lit.py --param build_config=. --param build_mode=Release -sv --param
llvm_site_config=/home/steve/llvm-build/test/lit.site.cfg --param
2009 Jul 10
2
[LLVMdev] Heads up! Working on bugpoint
I'm starting work on getting bugpoint working with remote execution
for arm. Is anyone else working on this?
David
2013 Oct 30
2
[LLVMdev] Symbolized ASan output on Android
If running ASan on the host architecture, we can symbolize output with:
export LLVM_SYMBOLIZER_PATH=`which llvm-symbolizer`
./myInstrumentedProgram
but on Android symbolizing is more complex. The bash script below is
a "hello world" for symbolizing ASan output on Android. Is there a
simpler way to do this?
# Execute the test and save its output
adb push
2013 Nov 23
2
[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
-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
2009 Jul 07
2
[LLVMdev] [PATCH] Fix for bugpoint -remote-client
Hello everyone,
Please find the patch attached.
This fixes the bugpoint -remote-client and adds a helper script for a remote run.
-Viktor
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ToolRunner.diff
Type: application/octet-stream
Size: 4210 bytes
Desc: not available
URL:
2010 Nov 25
2
[LLVMdev] using bugpoint in a complex ruby code build case
Hi all,
I've been running into what appears to be an optimization bug in llvm,
while compiling
the latest ruby 1.9.3 with the latest llvm/clang 2.9 version. From
hands on experimentation
I do know that the gvn pass for the "vm.c" compilation is the culprit
of the miscompilation
(clang -O2/-O3 options produce the miscompilation, however -O1 is
fine!). I've also tried
to
2007 Feb 21
2
[LLVMdev] bugpoint usage
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
2010 Dec 06
0
[LLVMdev] using bugpoint
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
2013 Nov 23
0
[LLVMdev] bugpoint question
----- 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
>
2009 Jul 08
0
[LLVMdev] [PATCH] Fix for bugpoint -remote-client
Thanks Viktor.
+ std::cout << "<run locally>" << std::flush;
This should use std::cerr and make sure it is wrapped inside the DEBUG
macro.
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?
Thanks,
Evan
On Jul 7,
2013 Oct 31
1
[LLVMdev] Symbolized ASan output on Android
Thanks for letting me know that this is in the works. This is
something that would make running ASan (and all other sanitizers I
assume) quite a bit more appealing on Android. If there's anything I
can do to help, please let me know. If you'd like to discuss in
person, I'll be at the Developers' Meeting next week.
-Greg
On Thu, Oct 31, 2013 at 1:58 PM, Alexey Samsonov
2016 Aug 19
2
Stop bugpoint from removing operand of metadata.
Hi,
I am trying to use bugpoint to reduce testcase. And bugpoint try to reduce
the number of operands for metadata, and this generate corrupted metadata:
*** Attempting to remove named metadata: Checking for crash with only these
named metadata nodes: llvm.dbg.cu llvm.module.flags llvm.ident: <crash>
Checking for crash with only these named metadata nodes: llvm.module.flags
llvm.ident:
2009 Oct 12
2
[LLVMdev] [PATCH] docs/Bugpoint.html: mention -debug-pass=Arguments
Hi,
when reporting
http://llvm.org/bugs/show_bug.cgi?id=5104
I spent quite a while trying to figure out what passes are used by
"-O1" so that I could give this list to bugpoint. It turns out
-debug-pass=Arguments is mentioned in docs/HowToSubmitABug.html but
under a chapter titled "Compile-time optimization bugs" which I
naively ignored since my bug was not a compile-time