search for: pubnam

Displaying 20 results from an estimated 66 matches for "pubnam".

Did you mean: putnam
2013 Jan 11
2
[LLVMdev] Restoring "pubnames" section in DWARF
We have customers that rely on the symbol information from the "pubnames" section in the DWARF data. Generation of this information was removed in this commit: commit dfa30e1ab243990eda4732a6dffb91e965e7a755 Author: Eric Christopher <echristo at apple.com> Date: Wed Nov 9 05:24:07 2011 +0000 Remove the pubnames section, no one consumes it....
2013 Jan 11
0
[LLVMdev] Restoring "pubnames" section in DWARF
>We have customers that rely on the symbol information from the >"pubnames" section in the DWARF data. Generation of this information >was removed in this commit: > >commit dfa30e1ab243990eda4732a6dffb91e965e7a755 >Author: Eric Christopher <echristo at apple.com> >Date: Wed Nov 9 05:24:07 2011 +0000 > > Remove the pubnames section,...
2017 Aug 08
2
DWARF: Ranges base address specifier entries & Gold's gdb-index 32 bit bug
...e? i.e. is it just gold that has the problem? > Yep, it's just gold when it's building the gdb-index (an accelerator table for GDB) > Conditioning on debugger tuning when it's not the debugger that has the > problem… icky. > It does. Though 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. > Assum...
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 creatio...
2013 Jan 11
2
[LLVMdev] Restoring "pubnames" section in DWARF
On Fri, Jan 11, 2013 at 1:49 PM, Robinson, Paul <Paul.Robinson at am.sony.com>wrote: > >We have customers that rely on the symbol information from the > >"pubnames" section in the DWARF data. Generation of this information > >was removed in this commit: > > > >commit dfa30e1ab243990eda4732a6dffb91e965e7a755 > >Author: Eric Christopher <echristo at apple.com> > >Date: Wed Nov 9 05:24:07 2011 +0000 > > > &g...
2017 Aug 07
4
DWARF: Ranges base address specifier entries & Gold's gdb-index 32 bit bug
...ult - 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 option...
2017 Aug 08
2
DWARF: Ranges base address specifier entries & Gold's gdb-index 32 bit bug
...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-pubnames in...
2015 Sep 07
0
[PATCH 4/4] builder: support Simple Streams v1.0 as index metadata
...n + filter_map ( + fun (prod, prod_desc) -> + let arch = object_get_string "arch" prod_desc in + let prods = Array.to_list (object_get_object "versions" prod_desc) in + let prods = filter_map ( + fun (rel, rel_desc) -> + let pubname = objects_get_string "pubname" [rel_desc; prod_desc] in + let items = object_find_object "items" rel_desc in + let disk_items = object_find_objects ( + function + | (("disk.img"|"disk1.img"), v) -> Some v +...
2013 Jan 11
0
[LLVMdev] Restoring "pubnames" section in DWARF
On 1/11/2013 4:04 PM, Eric Christopher wrote: > On Fri, Jan 11, 2013 at 1:49 PM, Robinson, Paul > <Paul.Robinson at am.sony.com <mailto:Paul.Robinson at am.sony.com>> wrote: > > I'd ask that it be made target-dependent, as I don't want it > (and apparently few do, which is why it was removed). > > > No worries there, it can be put under a flag
2013 Jan 11
1
[LLVMdev] Restoring "pubnames" section in DWARF
On Fri, Jan 11, 2013 at 2:07 PM, Krzysztof Parzyszek < kparzysz at codeaurora.org> wrote: > On 1/11/2013 4:04 PM, Eric Christopher wrote: > >> On Fri, Jan 11, 2013 at 1:49 PM, Robinson, Paul >> <Paul.Robinson at am.sony.com <mailto:Paul.Robinson at am.sony.**com<Paul.Robinson at am.sony.com>>> >> wrote: >> >> I'd ask that it be
2012 Mar 09
1
[LLVMdev] Dwarf info and .debug_pubnames section
...it's > useless for many reasons. Adding the code back in to generate it is > possible (it's > a fairly small commit that's easily reverted), but I see no reason to > have it generated > by default. What are you doing that involves looking for global > variables in the pubnames > section? > Thanks for the information. After I sent out the email, I saw the patch you reverted on viewVC. I have some proprietary code that looks at the debug info in an executable using libdwarf; It queries the debug info on demand with a variable name and uses dwarf_get_globals which,...
2008 Feb 29
0
[LLVMdev] llvm/test: suffix or operands invalid for `push'
>>> >>> Those are valid instructions in every x86-32 assembler I'm aware of. >>> Perhaps it needs a switch to put it in 32-bit mode? >> >> Yes, I have been able to confirm that's what's happening behind the >> scene. The switch would be --32, however after that, ld will try to >> link >> the 64-bit versions of libc and the C
2008 Feb 29
3
[LLVMdev] llvm/test: suffix or operands invalid for `push'
I do not know the configury stuff well enough to answer this, can someone else help? On Feb 28, 2008, at 1:55 AM, Joachim Durchholz wrote: > Am Mittwoch, den 27.02.2008, 14:31 -0800 schrieb Dale Johannesen: >> On Feb 27, 2008, at 2:12 PM, Joachim Durchholz wrote: >>> All error messages refer to one of the following four >>> instructions: >>> pushl %ebp
2015 Sep 07
5
[PATCH 0/4 v3] builder: support for Simple Streams metadata
Hi, this series adds a basic support for Simple Streams v1.0 metadata files. This makes it possible to create a repository .conf files with [cirros] uri=http://download.cirros-cloud.net format=simplestreams to read the latest version of each CirrOS image. Thanks, Pino Toscano (4): builder: add non-int revisions builder: add simple libyajl binding build: expose HAVE_YAJL to automake
2008 Feb 27
4
[LLVMdev] llvm/test: suffix or operands invalid for `push'
Hi all again, llvm is failing the 2006-11-30-NoCompileUnit and 2006-11-30-Pubnames tests on me. -m32 and --disable-multilib didn't change the outcome. Did I get the command wrong? I tried jo at kurier:~/Delta/llvm/test$ CFLAGS=--multilib make check See below for a transcript of the failed check. What next? Regards, Jo -- snip -- jo at kurier:~/Delta/llvm/test$ make c...
2015 Apr 15
2
[LLVMdev] About the "debugger target"
...ions with defaults based on the target platform. Other bits aren't but probably ought to be. Some of these are little things: - various Apple-defined attributes (DW_AT_APPLE_*) - TLS opcode (DW_OP_form_tls_address v. DW_OP_GNU_push_tls_address) Some are bigger things: - accelerator tables - pubnames/pubtypes Really these aren't so much _platform_ specific things as they are _debugger_ specific things. For example: - accelerator tables: default on for Darwin, but really on for LLDB. - pubnames/pubtypes: off for Darwin and PS4, but really on for GDB. We're co-opting platform as a pro...
2013 Aug 05
2
[LLVMdev] Many PPC64 failures with llvm 3.3
...LLVM :: CodeGen/PowerPC/stubs.ll [ 1553s] LLVM :: DebugInfo/debuglineinfo.test [ 1553s] LLVM :: DebugInfo/dwarf-public-names.ll [ 1553s] LLVM :: DebugInfo/dwarfdump-debug-frame-simple.test [ 1553s] LLVM :: DebugInfo/dwarfdump-inlining.test [ 1553s] LLVM :: DebugInfo/dwarfdump-pubnames.test [ 1553s] LLVM :: DebugInfo/dwarfdump-test.test [ 1553s] LLVM :: DebugInfo/dwarfdump-zlib.test [ 1553s] LLVM :: DebugInfo/llvm-symbolizer.test [ 1553s] LLVM :: DebugInfo/member-pointers.ll [ 1553s] LLVM :: DebugInfo/namespace.ll [ 1553s] LLVM :: DebugInfo/two-cus-from-...
2013 Nov 26
2
[LLVMdev] llvm-dwarfdump offsets
...rd using the same syntax to print the section relative offest for the unit header, then unit-relative offsets for the DIEs, but other than that this seems to me like a useful improvement. (I was going to use this change to help me print out the unit-relative offsets for types in type units to test pubnames + type units - obviously in the end the type units will be in their own section and unit relative and section relative will be synonymous again, but the change seems like goodness regardless) yes/no/maybe? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http:/...
2012 Mar 09
0
[LLVMdev] Dwarf info and .debug_pubnames section
On Mar 8, 2012, at 2:29 PM, Pranav Bhandarkar wrote: > Hi All, > > I just enabled the generation of dwarf debugging information for Hexagon. It > did not require much save for the setting of a flag in MCAsmInfo. > > However, now I see that the ".debug_pubnames" sections is not generated. I > did read discussion about the section not really being useful for debuggers > in terms of accelerated access, but I have code that uses libdwarf to check > for global variables. The particular libdwarf API queries the > ".debug_pubnames"...
2008 Mar 06
0
[LLVMdev] llvm/test: suffix or operands invalid for `push'
...t machinery, not in > > LLVM itself. > > Yep, I believe that. I haven't been following the whole thread very > closely, what specific tests are affected here? test/C++Frontend/2006-11-06-StackTrace.cpp test/C++Frontend/2006-11-30-NoCompileUnit.cpp test/C++Frontend/2006-11-30-Pubnames.cpp > Before making any significant and widespread changes to llvm/test, > please change one test and propose it as a model for other tests. The changes were actually very local: replace calls to gcc/g++/as with calls to %compile_c and %compile_cxx. I submitted bug reports with patches...