search for: ggnu

Displaying 9 results from an estimated 9 matches for "ggnu".

Did you mean: gnu
2017 Aug 08
2
DWARF: Ranges base address specifier entries & Gold's gdb-index 32 bit bug
Adrian: any thoughts? Has LLDB been fixed to support this yet? On Tue, Aug 8, 2017 at 6:33 AM Robinson, Paul <paul.robinson at sony.com> wrote: > My inclination would be to use "disable if 32-bit and –ggnu-pubnames" as > the default, > Unfortunately Nico points out that Chrome doesn't currently use -ggnu-pubnames :/ So to continue to work "out of the box" we'd have to broaden the surface to "disable if 32 bit and targeting gdb". -ggnu-pubnames makes gdb-index...
2017 Aug 08
2
DWARF: Ranges base address specifier entries & Gold's gdb-index 32 bit bug
...h to a lesser degree even gnu-pubnames isn't a perfect signal. One, I think, could use that even without a linker-generated gdb-index - presumably GDB's still faster by reading gnu-pubnames than by reading the raw DIEs to do lookup. > If that's the case then asking people to add –ggnu-pubnames seems okay. > Assuming that gets handed down through IR/metadata then the LTO problem > goes away too. > gnu-pubnames has such problems (it's done as a backend option, passed down from the clang driver via -mllvm -generate-gnu-dwarf-pub-sections, but they're already there...
2017 Aug 07
4
DWARF: Ranges base address specifier entries & Gold's gdb-index 32 bit bug
...default - with a flag to enable it for those who want it/can use it * Enable the feature everywhere - with a flag to disable it * Conditionally disable (or conditionally enable) the feature, with a flag to enable/disable it * best condition we probably have is "disabled if 32 bit and -ggnu-pubnames" (gnu-pubnames are necessary for efficient building of gdb-index, and isn't the default) 2) How to implement the flag: * backend option as it is currently (-mllvm -use-dwarf-ranges-base-address-specifier (maybe drop "-specifier" to make it a bit more terse)) * clang...
2017 Aug 08
2
DWARF: Ranges base address specifier entries & Gold's gdb-index 32 bit bug
...le it for > those who want it/can use it > * Enable the feature everywhere - with a flag to disable it > * Conditionally disable (or conditionally enable) the feature, with a > flag to enable/disable it > * best condition we probably have is "disabled if 32 bit and > -ggnu-pubnames" (gnu-pubnames are necessary for efficient building of > gdb-index, and isn't the default) > > > FWIW, we use -Wl,--gdb-index but had never heard of -ggnu-pubnames before > last week and don't use it (yet?). > PR34007 about the gold failure shows -ggnu-pubna...
2019 Jan 10
2
Slow debugger starts of LLVM tools
...eness too and we can more easily profile it. On Wed, Jan 9, 2019 at 2:48 PM Shoaib Meenai via llvm-dev < llvm-dev at lists.llvm.org> wrote: > I don't know about the issues with running being slow, but using a GDB > index greatly speeds up initial symbol loading. Compile with > `-ggnu-pubnames` and link with `-Xlinker --gdb-index` and you should get > significantly faster symbol load times. (I'd be curious to see if it helps > with the issues with run being slow as well.) > > On 1/9/19, 2:07 PM, "llvm-dev on behalf of David Greene via llvm-dev" < &g...
2019 Jan 09
2
Slow debugger starts of LLVM tools
David Jones via llvm-dev <llvm-dev at lists.llvm.org> writes: > GDB likes to load all symbols from shared libraries up front. And on > x86_64 your main executable is really just another shared library. Yes, but does gdb reload everything on each execution? Every time I execute "run" I see the same slow behavior. Loading the symbols for small tools like llvm-rc takes
2019 Jan 11
2
Slow debugger starts of LLVM tools
...easily profile it. > On Wed, Jan 9, 2019 at 2:48 PM Shoaib Meenai via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> I don't know about the issues with running being slow, but using a GDB >> index greatly speeds up initial symbol loading. Compile with >> `-ggnu-pubnames` and link with `-Xlinker --gdb-index` and you should get >> significantly faster symbol load times. (I'd be curious to see if it helps >> with the issues with run being slow as well.) >> >> On 1/9/19, 2:07 PM, "llvm-dev on behalf of David Greene via llvm-d...
2017 Feb 11
2
Asan self host problems: Failed to deallocate
Trying to run a self host "ninja check-clang" with ASan enabled I hit a /lot/ of errors like this (strangely I hit none of these in check-llvm, only in check-clang): Any ideas? ==10525==ERROR: AddressSanitizer failed to deallocate 0x10800 (67584) bytes at address 0x631000014800 ==10525==AddressSanitizer CHECK failed:
2017 Feb 15
2
Asan self host problems: Failed to deallocate
...program. CMAKE_AR:FILEPATH=/usr/bin/ar //The ASM compiler CMAKE_ASM_COMPILER:FILEPATH=/usr/local/google/home/blaikie/install/bin/clang //Flags used by the assembler during all build types. CMAKE_ASM_FLAGS:STRING= //Flags used by the assembler during debug builds. CMAKE_ASM_FLAGS_DEBUG:STRING=-g -ggnu-pubnames //Flags used by the assembler during release minsize builds. CMAKE_ASM_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG //Flags used by the assembler during release builds. CMAKE_ASM_FLAGS_RELEASE:STRING=-O3 -DNDEBUG //Flags used by the assembler during Release with Debug Info builds. CMAKE_ASM_FLA...