search for: debugopt

On Tue, Apr 14, 2015 at 03:20:08PM -0400, Gene Cumm wrote: > > I thought I would try to find out how pxelinux copes with this, by trying > > to insert printfs in pxe_init, but nothing gets printed. > > This is normal. Can you give me hint as to why setting > > DEBUGOPT = -DDEBUG=1 -DDEBUG_STDIO -DCORE_DEBUG=1 changes that state of normality? (AFAICT dprintf.h defines dprintf to printf, so why wouldn't using printf directly work? printf.o gets built regardless of DEBUG settings AFAICT.) > > From looking at com32/include/dprintf.h, it looks as though al...

Hi, I'm following http://llvm.org/docs/SourceLevelDebugging.html#debugopt to do the dbgopt testing. But seems, there is something wrong with the Makefile, it told me : llvm-gcc sse.expandfft.c -g --emit-llvm -c -o Output/sse.expandfft.bc llvm-gcc: sse.expandfft.c: No such file or directory llvm-gcc: no input files Am I missing something, like the configure option? ---...

...t is having boot trouble has three instances of "!PXE" in the chunk of memory that "Method D" should look at. I thought I would try to find out how pxelinux copes with this, by trying to insert printfs in pxe_init, but nothing gets printed. I can spew lots of output if I set DEBUGOPT = -DDEBUG=1 -DDEBUG_STDIO -DCORE_DEBUG=1 but given that this box doesn't have a serial port, anything I add will whizz off the screen. >From looking at com32/include/dprintf.h, it looks as though all this does is to define dprintf to printf, so why is it that if don't define DEBUG_STDI...

...nsertions(+), 2 deletions(-) >> >> diff --git a/mk/syslinux.mk b/mk/syslinux.mk >> index 337560b..9ca74b1 100644 >> --- a/mk/syslinux.mk >> +++ b/mk/syslinux.mk >> @@ -82,11 +82,11 @@ ARCH ?= $(strip $(SUBARCH)) >> GCCWARN = -W -Wall -Wstrict-prototypes $(DEBUGOPT) >> >> # Common stanza to make gcc generate .*.d dependency files >> -MAKEDEPS = -Wp,-MT,$@,-MD,$(dir $@).$(notdir $@).d >> +MAKEDEPS = -MT $@ -MD >> >> # Dependencies that exclude system headers; use whenever we use >> # header files from the platform. &...

...mail.com> --- mk/syslinux.mk | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/mk/syslinux.mk b/mk/syslinux.mk index 337560b..9ca74b1 100644 --- a/mk/syslinux.mk +++ b/mk/syslinux.mk @@ -82,11 +82,11 @@ ARCH ?= $(strip $(SUBARCH)) GCCWARN = -W -Wall -Wstrict-prototypes $(DEBUGOPT) # Common stanza to make gcc generate .*.d dependency files -MAKEDEPS = -Wp,-MT,$@,-MD,$(dir $@).$(notdir $@).d +MAKEDEPS = -MT $@ -MD # Dependencies that exclude system headers; use whenever we use # header files from the platform. -UMAKEDEPS = -Wp,-MT,$@,-MMD,$(dir $@).$(notdir $@).d +UMAK...

...ight have 3 that are overwriting each other. 2) Method D is quite the fall back. > I thought I would try to find out how pxelinux copes with this, by trying > to insert printfs in pxe_init, but nothing gets printed. This is normal. > I can spew lots of output if I set > > DEBUGOPT = -DDEBUG=1 -DDEBUG_STDIO -DCORE_DEBUG=1 > > but given that this box doesn't have a serial port, anything I add will > whizz off the screen. Serial or some sort of IP KVM with logging is ideal. > From looking at com32/include/dprintf.h, it looks as though all this does is > to...

...0:08PM -0400, Gene Cumm wrote: >> > I thought I would try to find out how pxelinux copes with this, by trying >> > to insert printfs in pxe_init, but nothing gets printed. >> >> This is normal. > > Can you give me hint as to why setting > >> > DEBUGOPT = -DDEBUG=1 -DDEBUG_STDIO -DCORE_DEBUG=1 > > changes that state of normality? What commit ID or numerical version? -- -Gene

...-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/mk/syslinux.mk b/mk/syslinux.mk > index 337560b..9ca74b1 100644 > --- a/mk/syslinux.mk > +++ b/mk/syslinux.mk > @@ -82,11 +82,11 @@ ARCH ?= $(strip $(SUBARCH)) > GCCWARN = -W -Wall -Wstrict-prototypes $(DEBUGOPT) > > # Common stanza to make gcc generate .*.d dependency files > -MAKEDEPS = -Wp,-MT,$@,-MD,$(dir $@).$(notdir $@).d > +MAKEDEPS = -MT $@ -MD > > # Dependencies that exclude system headers; use whenever we use > # header files from the platform. > -UMAKEDEPS = -Wp,-MT,$@...

...) >>> >>> diff --git a/mk/syslinux.mk b/mk/syslinux.mk >>> index 337560b..9ca74b1 100644 >>> --- a/mk/syslinux.mk >>> +++ b/mk/syslinux.mk >>> @@ -82,11 +82,11 @@ ARCH ?= $(strip $(SUBARCH)) >>> GCCWARN = -W -Wall -Wstrict-prototypes $(DEBUGOPT) >>> >>> # Common stanza to make gcc generate .*.d dependency files >>> -MAKEDEPS = -Wp,-MT,$@,-MD,$(dir $@).$(notdir $@).d >>> +MAKEDEPS = -MT $@ -MD >>> >>> # Dependencies that exclude system headers; use whenever we use >>> # header...

Hi, I would like to know how much effect these stoppoint calls have on the optimization of the bytecode? DOes insertion of debugging info cause opportunities for optimization (especially interprocedural dead code elimination and interprocedural constant propogation) to be reduced? The -g code is not very readable, so I am not able to confirm this by my own experiment. Thanks! Nikhil On Sat,

...ug info influence the symbol names in assembly file, for example? > >> > This obviously only catches badness that happens in the LLVM >> > optimizer, >> > > There is an establish way to check this. See > http://llvm.org/docs/SourceLevelDebugging.html#debugopt > > That's great, thanks. >> > if the code generator is broken, we'll need something more >> > sophisticated that strips debug info out of the .s file. In any >> > case, this is a good place to start, and should be turned into a >> > llvm-...

...s Scanning Script > > Following the way proposed by Chris, it is good to have a script to > > scan the standard LLVM transform pass list. We can get the standard > > compile optimization pass list by: > > > You can use http://llvm.org/docs/SourceLevelDebugging.html#debugopt as > a starting point here. > Ok. >> > >> > $ opt -std-compile-opts -debug-pass=Arguments foo.bc > /dev/ >> > null ... ... > 2.2 Phase 2: New Pass to Strip Debug Information > > LLVM already has a transform pass "-strip-debug",...

On May 30, 2011, at 11:11 AM, trash-stuff at gmx.de wrote: > Hi all, > > I am processing DWARF line and column information in (x86 and ARM) executables in order to produce a mapping from the machine instructions back to the original source code (C/C++). Using the line numbers is quite straightforward ("libdwarf" [1] is doing the work me.) But when comparing the column numbers

Hi all, I am processing DWARF line and column information in (x86 and ARM) executables in order to produce a mapping from the machine instructions back to the original source code (C/C++). Using the line numbers is quite straightforward ("libdwarf" [1] is doing the work me.) But when comparing the column numbers (extracted from the DWARF line table) with the corresponding source

...ides information to accurately read the source-level state of the program, regardless of which LLVM optimizations have been run*, and without any modification to the optimizations themselves." [1]) Any other ideas? Best regards Adrian [1] http://llvm.org/docs/SourceLevelDebugging.html#debugopt -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110531/a4b1e0d5/attachment.html>

Hi, I've been thinking about how to keep the line number with the llvm transform/Analysis passes. Basically, I agree with Chris's notes ( http://www.nondot.org/sabre/LLVMNotes/DebugInfoImprovements.txt), and I will follow his way to turn on the line number information when optimization enabled. Here is a detailed proposal: 1. Introduction At the time of this writing, LLVM's

> On Aug 19, 2014, at 1:32 PM, Rafael Espíndola <rafael.espindola at gmail.com> wrote: > >>> * Nobs for which there is not a single right answer for all users. >>> There are very few of these currently and we expect it to remain like >>> that. These should not use cl::opt or static storage at all. They >>> should be an option passed to the