similar to: [LLVMdev] RFC: Bugpoint Patch

On Feb 25, 2009, at 4:59 PMPST, Bill Wendling wrote: > I'm running into a problem where I need to have the "gcc" that's > executed by "bugpoint" take certain arguments that aren't applicable > to "llc". So, I came up with this patch, that adds a new flag > "-gcc-tool-args". It's similar to "-tool-args" but passes the

On Feb 25, 2009, at 6:01 PM, Dale Johannesen wrote: > On Feb 25, 2009, at 4:59 PMPST, Bill Wendling wrote: > >> I'm running into a problem where I need to have the "gcc" that's >> executed by "bugpoint" take certain arguments that aren't applicable >> to "llc". So, I came up with this patch, that adds a new flag >>

On Feb 26, 2009, at 1:40 AMPST, Bill Wendling wrote: > On Feb 25, 2009, at 6:01 PM, Dale Johannesen wrote: > >> On Feb 25, 2009, at 4:59 PMPST, Bill Wendling wrote: >> >>> I'm running into a problem where I need to have the "gcc" that's >>> executed by "bugpoint" take certain arguments that aren't applicable >>> to

Hi all, Is anyone else seeing tests in the Multisource/Applications directory failing with something looking like this: /Users/wendling/llvm/llvm.obj/Debug/bin/gccld -L/Users/wendling/llvm/ llvm-gcc4.install/lib/gcc/powerpc-apple-darwin8.8.0/3.4-llvm -L/ Users/wendling/llvm/llvm-gcc4.install/lib Output/siod.linked.bc -lc -lpthread -lltdl -lm -o Output/siod.llvm gccld: warning: Cannot

On Sun, 29 Oct 2006, Bill Wendling wrote: > Is there a way to make bugpoint use gccld (or the equivalent with llc > flags)? In a multisource/external dir, use 'make bugpoint-gccld'. In singlesource, use 'make Output/progname.bugpoint-gccld'. -Chris -- http://nondot.org/sabre/ http://llvm.org/

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

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

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

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':

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' [ Good! This is progress! ] *** You can

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

On Feb 3, 2009, at 2:35 PMPST, Mike Stump wrote: > On Feb 3, 2009, at 2:28 PM, Kasra wrote: >> I was looking around the LLVM instruction set and I failed to find >> ROL and ROR instructions. Is there any plans on adding these >> instructions to LLVM? > > Not sure what you mean: He's referring to the LLVM IR, I think, and it's true that doesn't have

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

--- 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/bugpoint.cpp +++ b/tools/bugpoint/bugpoint.cpp @@ -67,7 +67,7 @@ int main(int argc,

The LegalizeDAG.cpp file has this code in SelectionDAGLegalize::PromoteNode: case ISD::BSWAP: { unsigned DiffBits = NVT.getSizeInBits() - OVT.getSizeInBits(); Tmp1 = DAG.getNode(ISD::ZERO_EXTEND, dl, NVT, Tmp1); Tmp1 = DAG.getNode(ISD::BSWAP, dl, NVT, Tmp1); Tmp1 = DAG.getNode(ISD::SRL, dl, NVT, Tmp1, DAG.getConstant(DiffBits, TLI.getShiftAmountTy()));

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

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

On Jul 8, 2009, at 12:42 AM, Viktor Kutuzov wrote: > 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

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:

----- 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$ >