search for: fverbose

...ild 5623) (LLVM build). # GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072 # options passed: -D__DYNAMIC__ -fPIC -Wformat -Wformat-security # -Wno-format-extra-args -Wno-format-zero-length -Wno-nonnull # -mmacosx-version-min=10.5.6 -mtune=generic -march=nocona -auxbase # -fverbose-asm -D__private_extern__=extern # options enabled: -fPIC -falign-jumps-max-skip -falign-loops # -falign-loops-max-skip -fargument-alias -fbranch-count-reg -fcommon # -fearly-inlining -feliminate-unused-debug-types -femit-class-debug-always # -fexceptions -ffunction-cse -fgcse-lm -fglobal-alloc-pre...

.../llvm.org/bugs/show_bug.cgi?id=17465 suggests some workarounds. A comment also points to a patch that I could not retrieve. - Proposal This proposal currently spans LLVM and clang. -- clang/FE changes For clang it would simply mean to add a flag like -fsource-asm or maybe extend the meaning of -fverbose-asm (like it will happen in GCC 7 but see some further comments below). This flag would make sure that the minimal amount of debug information is generated. Currently this means enabling -gline-tables-only in absence of any other debugging flag specified. A flag -masm-source for communicating the d...

When I am constructing sequences of instructions during custom lowering, I would like to be able to also add a comment that appears in the generated assembly with '-S -fverbose-asm'. There is a large set of 'add*' functions to attach additional information to the MI, but I don't see one for adding comments. Is there a method I can call to attach an arbitrary string ('StringRef', 'const char*', 'Twine') to an MI with 'BuildM...

Hi Alexandra, > I upgraded to llvm 2.8 and when I generate *.ll files from C/C++ with > clang -S -emit-llvm I obtain a *.ll file in which instructions and > basicblocks have no names. > I tried as well compiling with the -g option, but no names were given. with dragonegg using -fverbose-asm causes names to be generated in the IR. Maybe clang could do this to? Ciao, Duncan.

...atthias > On Feb 3, 2018, at 4:40 AM, Martin J. O'Riordan via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > When I am constructing sequences of instructions during custom lowering, I would like to be able to also add a comment that appears in the generated assembly with ‘-S -fverbose-asm’. There is a large set of ‘add*’ functions to attach additional information to the MI, but I don’t see one for adding comments. > > Is there a method I can call to attach an arbitrary string (‘StringRef’, ‘const char*’, ‘Twine’) to an MI with ‘BuildMI’ or after? > > Thanks, &gt...

...that can't > be synthesized by the asmprinter. Again, we only emit some of this > with > special debug flags so we don't carry the original IR around in > comments all > the time. :) Sure, I understand that comments in general only get turned on with something like -fverbose-asm. But where/how do you expect this information to be propagated onto the machineinstrs? For now, lets go forward with the plan of having the asmprinter generate the comments. It sounds like it can cover at least 75% of what you're interested in, and the other cases probably have bet...

Hello, I upgraded to llvm 2.8 and when I generate *.ll files from C/C++ with clang -S -emit-llvm I obtain a *.ll file in which instructions and basicblocks have no names. I tried as well compiling with the -g option, but no names were given. In the release notes it is indicated to use "--show-annotations" to print the number of uses. Is there something similar for assigning names to

...hesized by the asmprinter. Again, we only emit some of this > > with > > special debug flags so we don't carry the original IR around in > > comments all > > the time. :) > > Sure, I understand that comments in general only get turned on with > something like -fverbose-asm. But where/how do you expect this > information to be propagated onto the machineinstrs? Some comments are on all the time, but those I think we can do with asmprinter, as you suggest. I have patches that propagate comments from Instructions to SDNodes to MachineInstrs. Again, after answ...

...#39;Riordan via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org> > wrote: > > > > When I am constructing sequences of instructions during custom lowering, I would like to be able to also add a comment that appears in the generated assembly with ‘-S -fverbose-asm’. There is a large set of ‘add*’ functions to attach additional information to the MI, but I don’t see one for adding comments. > > > > Is there a method I can call to attach an arbitrary string (‘StringRef’, ‘const char*’, ‘Twine’) to an MI with ‘BuildMI’ or after? > > &...

...me-pointer -fno-optimize-sibling-calls -fno-var-tracking-assignments -g -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes -DKBUILD_BASENAME='"bounds"' -DKBUILD_MODNAME='"bounds"' -fverbose-asm -E -o kernel/bounds.i kernel/bounds.c In file included from include/asm-generic/bug.h:13:0, from ./arch/arm64/include/asm/bug.h:62, from include/linux/bug.h:4, from include/linux/page-flags.h:9, from kernel/bounds.c:9: include/...

...-git/bin/gcc LC=/opt/llvm-svn/bin/llvm-config export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$($LC --libdir) GCC=$CC LLVM_CONFIG=$LC ENABLE_LLVM_PLUGINS=1 DRAGONEGG_DEBUG=1 make -j4 $CC -fplugin=./dragonegg.so \ -fplugin-arg-dragonegg-debug-pass-arguments \ -ftime-report \ -fverbose-asm \ -fplugin-arg-dragonegg-enable-gcc-optzns \ -fplugin-arg-dragonegg-emit-ir \ -S \ test/hello.c \ -wrapper gdb,--args hello.s (LLVM IR, the extension name is not important) ; ModuleID = 'test/hello.c' source_filename = "test/hello.c&q...

...r. Again, we only emit some of this >>> with >>> special debug flags so we don't carry the original IR around in >>> comments all >>> the time. :) >> >> Sure, I understand that comments in general only get turned on with >> something like -fverbose-asm. But where/how do you expect this >> information to be propagated onto the machineinstrs? > > Some comments are on all the time, but those I think we can do with > asmprinter, as you suggest. Yep. > I have patches that propagate comments from Instructions to SDNodes to >...

...> I upgraded to llvm 2.8 and when I generate *.ll files from C/C++ with >> clang -S -emit-llvm I obtain a *.ll file in which instructions and >> basicblocks have no names. >> I tried as well compiling with the -g option, but no names were given. > > with dragonegg using -fverbose-asm causes names to be generated in the IR. > Maybe clang could do this to? This isn't a 2.8 change, the issue is that release-without-asserts builds don't add names on instructions (because IRBuilder gets a different argument). -Chris

...ig features, there are dozens smaller features in LLVM 2.7, such as support for non-temporal stores, 16-bit half-float support, much improved X86 tail calls, better inliner heuristics, an improved implementation of __builtin_object_size, many optimizer improvements, much nicer comments produced in -fverbose-asm mode, debug info support in the JIT, substantial footprint reductions for the LLVM compiler itself (useful for clients of the JIT), full NEON support in the ARM backend, support for building LLVM as a single big dynamic library, and more. Please see the release notes for more details. Beyond...

...mize-sibling-calls -fno-var-tracking-assignments -g > -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow > -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes > -DKBUILD_BASENAME='"bounds"' -DKBUILD_MODNAME='"bounds"' > -fverbose-asm -E -o kernel/bounds.i kernel/bounds.c > In file included from include/asm-generic/bug.h:13:0, > from ./arch/arm64/include/asm/bug.h:62, > from include/linux/bug.h:4, > from include/linux/page-flags.h:9, > from ke...

On Monday 13 July 2009 13:13, Chris Lattner wrote: > > We're not going to submit our line number stuff anyway (it's too > > much of a > > hack) but we would like the comment infrastructure to be there. > > DebugLoc is there. The transition isn't complete at the LLVM IR > level, but it is at the MachineInstr level AFAIK. Well, the IR level is pretty

...ns what the personality function and unwind libraries do. Well, "read" might be a bad way of putting it. You should definitely familiarize yourself with each document. But I would look to understand why the FDE looks like it does or what the format of the exception handling table means (-fverbose-asm gives extra information to help with this). For specifics on how LLVM generates this information, look at these files: * lib/CodeGen/AsmPrinter/DwarfException.cpp This outputs the CIE, FDE, and exception handling tables. * lib/Target/X86/X86RegisterInfo.cpp The "X86RegisterInfo::emi...

Hi, I'm trying to learn all that I can about exception handling from the compiler's point of view. Although much has been written about compiler theory in general -- parsing, code generation, you name it -- I can find almost nothing on the specific problem of exception handling support. In fact, the most informative document I've been able to find so far is "Bill's

On 9 July 2016 at 08:30, Markus Mayer <markus.mayer at broadcom.com> wrote: > On 9 July 2016 at 05:04, Luis de Bethencourt <luisbg at osg.samsung.com> wrote: >> On 08/07/16 23:43, Markus Mayer wrote: >>> Add a collection of generic functions to convert strings to lowercase >>> or uppercase. >>> >>> Changing the case of a string (with or

Currently we have RH7.3 with compiler gcc 2.96.x My mission, should I choose to accept it, involves moving our embedded application to CentOS 4.1 with gcc 3.x Problem is that about 1/2 million lines of code that gcc 2.96 accepts gives fatal fits to the gcc 3.x compiler from CentOS 4.1 I don't know how many fatal fits, as some disguise others etc. "Can't find register to