search for: howtosubmitabug

Hi Jan, From what I understand, except https://llvm.org/docs/HowToSubmitABug.html#incorrect-code-generation , the rest of https://llvm.org/docs/HowToSubmitABug.html seems fine. C backend is removed from the code base, and I don't know what is the proper way to debug incorrect code generation. Since you mentioned clang crash, I think you can tell the clang user start...

Hi all, I was reading through the docs as I wanted to give advice on submitting bug report to clang user asking for help with clang crash at cfe-users mailing list. https://llvm.org/docs/HowToSubmitABug.html#crashes-the-compiler <https://llvm.org/docs/HowToSubmitABug.html#crashes-the-compiler> I am not really familiar with most of that stuff but the page still mentioned GCC and seems like most of it is 3-5 years old. It might be worthwhile if someone more knowledgeable could take a look at...

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 bug. How about mentioning this more explicitely in the bugpoint documentation along the lines of the attached patch? best regards, Timo Lindfors -------------- n...

...of this? > section-relative offsets should be used on COFF. Well, not everywhere it seems: for references into the .text section, gcc still uses .long <offset from beginning of .text> > Can you fill the PR with short reproducer? > Are you referring to this: http://llvm.org/docs/HowToSubmitABug.html ? Sorry, I'm new here. Vadim -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130606/79f661d7/attachment.html>

...ou can do this: % opt -mem2reg < orig.bc > m2r.bc % opt -load=... -metasplit < m2r.bc > output.bc And see if it crashes in mem2reg or in your pass. To narrow your testcase down further, we recommend the use of bugpoint, the automatic test case reducer: http://llvm.cs.uiuc.edu/docs/HowToSubmitABug.html In this case, this should work: % bugpoint -load=... -mem2reg -metasplit orig.bc -- Misha Brukman :: http://misha.brukman.net :: http://llvm.cs.uiuc.edu

I am investigating some inlining issue, so I did llvm-gcc aaa.c bbb.c ... nnn.c -o output opt -inline -inline-threshold=xxx < output.bc | llc -march=c > output_inline.c 1) I noticed that even if I set xxx to 0 or even a very small negative number, many functions are eliminated. I am wondering if these functions are inlined by the frontend, or identified as deadcode. For instance,

...bc" it will only inline. Note that if you say "opt < old.bc > new.bc" opt will do nothing. This differs from gccas and gccld which have a built-in list of optimizations that they run, which you can get a list of if you follow the directions here: http://llvm.cs.uiuc.edu/docs/HowToSubmitABug.html#gccas http://llvm.cs.uiuc.edu/docs/HowToSubmitABug.html#gccld or just read their source code. John Criswell wrote: > Long Fei wrote: > >> >> I am investigating some inlining issue, so I did >> >> llvm-gcc aaa.c bbb.c ... nnn.c -o output >> opt -inline -i...

...a crash when compiling the llvm-gcc frontend. According to the bugpoint documentation, bugpoint is used to debug "optimizer crashes, miscompilations by optimizers, or bad native code generation," which seems like it implies that the frontend compiles. Also, the http://llvm.org/docs/HowToSubmitABug.html documentation seems to only address bugs that occur once the frontend is compiled. So, I'm a little unclear what I should submit when filing the bug. If I'm missing something or incorrect, please correct me. Ryan Chris Lattner wrote: > On Wed, 22 Aug 2007, Ryan M. Lefever w...

...M passes >are responsible for the failure or what part of the input is triggering >the problem. Bugpoint automates the process of narrowing down where a >bug is and what input is triggering it. > >For more information, you can read about bugpoint at: > >http://llvm.org/docs/HowToSubmitABug.html >http://llvm.org/docs/CommandGuide/html/bugpoint.html > >-- John T. > >> Thank you. >> _______________________________________________ >> LLVM Developers mailing list >> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >> http://lists.cs.uiuc.edu...

...te that if you say "opt < old.bc > new.bc" opt > will do nothing. > > This differs from gccas and gccld which have a built-in list of > optimizations that they run, which you can get a list of if you follow > the directions here: > > http://llvm.cs.uiuc.edu/docs/HowToSubmitABug.html#gccas > http://llvm.cs.uiuc.edu/docs/HowToSubmitABug.html#gccld > > or just read their source code. > > > John Criswell wrote: > >> Long Fei wrote: >> >>> >>> I am investigating some inlining issue, so I did >>> >>> llvm-g...

...rying to figure > out which stage is creating this issue? > > The input LLVM-ir is in test.ll. > > The version with no optimizations looks correct, but the one using > -std-compile-opts produces a CFG with an infinite loop. You might want to try bugpoint; see http://llvm.org/docs/HowToSubmitABug.html and http://llvm.org/docs/Bugpoint.html for more info. For your specific case, you'll need to add a "main" of some sort, and pass something like -timeout 2 so that it doesn't take forever. That said, it's a lot more convenient than doing a manual binary search. -Eli

...Fri, Jun 24, 2011 at 9:12 AM, Karel Gardas<karel.gardas at centrum.cz> wrote: >> My question is if it is a known bug or unknown in which case where to >> report it and if also include compiled *.bc file or not. > > Haven't seen it before... see > http://llvm.org/docs/HowToSubmitABug.html , and please do include the > .bc file (assuming you don't mind it being publicly visible). .bc file is free as it is produced from the free code. However shall I submit bug in a special way as described on your recommended page? If so, then please tell me what to use "crashing...

>> Can you fill the PR with short reproducer? > Are you referring to this: http://llvm.org/docs/HowToSubmitABug.html ? Yes. -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

FYI: I just posted a short document with instructions on how to submit a proper bug report. If you run into problems using LLVM, please let us know. The instructions indicate steps to properly narrow down the bug, which will make life easier for the bug-fixer. :) http://llvm.cs.uiuc.edu/docs/HowToSubmitABug.html -Chris -- http://llvm.cs.uiuc.edu/ http://www.nondot.org/~sabre/Projects/

...t am I supposed to do now ? This means that one of the passes in gccas or gccld is mis-optimizing the code, since the unoptimized code works. See the "debugging gccas" and "debugging gccld" sections of the "How To Submit a Bug" document: http://llvm.cs.uiuc.edu/docs/HowToSubmitABug.html#gccas http://llvm.cs.uiuc.edu/docs/HowToSubmitABug.html#gccld -- Misha Brukman :: http://misha.brukman.net :: http://llvm.cs.uiuc.edu

...opt -load=... -metasplit < m2r.bc > output.bc > > > > And see if it crashes in mem2reg or in your pass. To narrow your > > testcase down further, we recommend the use of bugpoint, the automatic > > test case reducer: > > > > http://llvm.cs.uiuc.edu/docs/HowToSubmitABug.html > > > > In this case, this should work: > > > > % bugpoint -load=... -mem2reg -metasplit orig.bc > > > > -- > > Misha Brukman :: http://misha.brukman.net :: http://llvm.cs.uiuc.edu > > > > _______________________________________________ &gt...

...in the README.LLVM file. Does > anyone have any ideas on what the problem is? Any help would be greatly > appreciated. It looks like you hit a bug. Please reduce the bug (at least get a .ii file for the crash, better to use bugpoint to reduce it) as described here: http://llvm.org/docs/HowToSubmitABug.html If you reduce the bug well, you can often get a fix within a day. -Chris > > ----------- compilation errors ------------------ > /home/crhc3/lefever/llvm/cvs-070820/llvm-gcc-4.0_obj/gcc/xgcc > -shared-libgcc > -B/home/crhc3/lefever/llvm/cvs-070820/llvm-gcc-4.0_obj/gcc/ -nostd...

...ks (output is correct) 3. use the JIT to run the BC, test that it works properly (output is correct) 4. Repeat steps 1-3 with -O1, -O2, until it fails Once you identified at which stage the problem occurs, you can try the instructions here to further narrow down the problem: http://llvm.org/docs/HowToSubmitABug.html#codegen Best regards, --Edwin

...lt; orig.bc > m2r.bc > % opt -load=... -metasplit < m2r.bc > output.bc > > And see if it crashes in mem2reg or in your pass. To narrow your > testcase down further, we recommend the use of bugpoint, the automatic > test case reducer: > > http://llvm.cs.uiuc.edu/docs/HowToSubmitABug.html > > In this case, this should work: > > % bugpoint -load=... -mem2reg -metasplit orig.bc > > -- > Misha Brukman :: http://misha.brukman.net :: http://llvm.cs.uiuc.edu > > _______________________________________________ > LLVM Developers mailing list > LLVMdev...

What exactly are the standard compile options that are implemented when using -std-compile-opts? The reason I'm asking is it seems that -std-compile-opts creates some CFG graphs that are invalid and should not be created and I am trying to figure out which stage is creating this issue? The input LLVM-ir is in test.ll. The version with no optimizations looks correct, but the one using