similar to: [LLVMdev] LLVM generates broken debug info on Windows

Hi, I 'm trying to figure out why LLVM emits broken DWARF debug info on Windows. When I load executable in gdb it says "DW_FORM_strp pointing outside of .debug_str section [in module ... ]" It looks like this issue had been previously reported here [1]<http://lists.cs.uiuc.edu/pipermail/cfe-dev/2012-October/025291.html>, [2]

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

W dniu 2012-10-26 16:55, Daniel Kłobuszewski pisze: > Hello, > > Recently I found binaries produced with LLVM impossible to debug under > Windows. This was probably related to the following bug: > http://llvm.org/bugs/show_bug.cgi?id=13636 > > Asm generated from .ll files revealed that some offsets to debug > information were incorrect: they were absolute instead of

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

This didn't work as I tried with 197.parser. it works without "-Wl,-disable-opt" switch though. [197.parser]$ llvm-gcc analyze-linkage.c and.c build-disjuncts.c extract-links.c fast-match.c idiom.c main.c massage.c parse.c post-process.c print.c prune.c read-dict.c utilities.c xalloc.c word-file.c strncasecmp.c -Wa,-disable-opt -Wl,-disable-opt -lm -o llvm_parser [197.parser]$

On Wed, Jun 23, 2004 at 03:50:09PM -0500, Patrick Meredith wrote: > MetaSplit is an anlysis I just finished writing. It doesn't alter > anything, all it does is build a set of "program instructions". For > some reason even though if I run it with any other combination of > passes I've found, anytime I run it with mem2reg I get a seg fault in > dyn_cast!

Chris, I'm a little confused. I am experiencing 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

On Mon, 11 Jul 2005, Long Fei wrote: > > This didn't work as I tried with 197.parser. it works without > "-Wl,-disable-opt" switch though. > > [197.parser]$ llvm-gcc analyze-linkage.c and.c build-disjuncts.c > extract-links.c fast-match.c idiom.c main.c massage.c parse.c post-process.c > print.c prune.c read-dict.c utilities.c xalloc.c word-file.c

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/

On Thu, Oct 16, 2008 at 12:03 PM, Villmow, Micah <Micah.Villmow at amd.com> wrote: > 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

On 06/24/11 06:53 PM, Eli Friedman wrote: > On 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

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

On Wed, 22 Aug 2007, Ryan M. Lefever wrote: > I checked llvm-gcc 4.0 out from svn yesterday and am compiling it on 3 > different machines. I was able to compile it on 2 of the machines, but > the compilation failed on the third machine with the errors below. The > machine that the compilation failed on is running Fedora Core 4. The > processor is a AMD Athlon(tm) 64 Processor

On 02/01/2010 01:13 PM, Kristaps Straupe wrote: > Hello again! > > We have fetched the latest llvm sources from repository and the > original problem has went away. Though now we are facing a new problem > with interpreter on the following c code: > > -------------- > #include <stdarg.h> > #include <stdio.h> > > void doTheThing(int dummy, ...) > {

On Wed, 23 Jun 2004, Patrick Meredith wrote: > What's different about code that's been mem2reg'd from straight front end > code, or anything that mem2reg hasn't been run on? PHINODES! Yup, front-ends generally don't produce SSA form. :) > It appears to be crashing when I try to cast a Value* that's really a > BB* (from the PHInode operands) to a User*,

What's different about code that's been mem2reg'd from straight front end code, or anything that mem2reg hasn't been run on? PHINODES! It appears to be crashing when I try to cast a Value* that's really a BB* (from the PHInode operands) to a User*, insteresting since I am dyn_casting. I just caught this on cerr though (printing out what the Value* was each time). Let me

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 with

Thanks for the bug report. The attached file isn't helpful for reproducing the problem. I don't have all the header files that are included, so I can't just try to run it through my version of llvm-gcc and see what happens. At a minimum, please attach the preprocessed source file along with the complete llvm-gcc command line that you used to compile it. That would

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

Somehow it fails with operand out of bounds when the number of operands is 2 and I am asking for the second operand. ----- Original Message ----- From: "Chris Lattner" <sabre at nondot.org> To: <llvmdev at cs.uiuc.edu> Sent: Wednesday, June 23, 2004 4:24 PM Subject: Re: [LLVMdev] weird issue with mem2reg, should have guessed > On Wed, 23 Jun 2004, Patrick Meredith