aboutsummaryrefslogtreecommitdiff
path: root/libctf/NEWS
diff options
context:
space:
mode:
authorNick Alcock <nick.alcock@oracle.com>2022-03-16 15:29:25 +0000
committerNick Alcock <nick.alcock@oracle.com>2022-03-23 13:48:32 +0000
commit203bfa2f6bd275df4089131bac0a17c278c37a1a (patch)
treecb4b22f42e78f3a9522a4e6b6f149fcc40ae933e /libctf/NEWS
parenta12c988767e5bd6b6a15dd6ca5e3b277f5627c64 (diff)
downloadgdb-203bfa2f6bd275df4089131bac0a17c278c37a1a.zip
gdb-203bfa2f6bd275df4089131bac0a17c278c37a1a.tar.gz
gdb-203bfa2f6bd275df4089131bac0a17c278c37a1a.tar.bz2
include, libctf, ld: extend variable section to contain functions too
The CTF variable section is an optional (usually-not-present) section in the CTF dict which contains name -> type mappings corresponding to data symbols that are present in the linker input but not in the output symbol table: the idea is that programs that use their own symbol- resolution mechanisms can use this section to look up the types of symbols they have found using their own mechanism. Because these removed symbols (mostly static variables, functions, etc) all have names that are unlikely to appear in the ELF symtab and because very few programs have their own symbol-resolution mechanisms, a special linker flag (--ctf-variables) is needed to emit this section. Historically, we emitted only removed data symbols into the variable section. This seemed to make sense at the time, but in hindsight it really doesn't: functions are symbols too, and a C program can look them up just like any other type. So extend the variable section so that it contains all static function symbols too (if it is emitted at all), with types of kind CTF_K_FUNCTION. This is a little fiddly. We relied on compiler assistance for data symbols: the compiler simply emits all data symbols twice, once into the symtypetab as an indexed symbol and once into the variable section. Rather than wait for a suitably adjusted compiler that does the same for function symbols, we can pluck unreported function symbols out of the symtab and add them to the variable section ourselves. While we're at it, we do the same with data symbols: this is redundant right now because the compiler does it, but it costs very little time and lets the compiler drop this kludge and save a little space in .o files. include/ * ctf.h: Mention the new things we can see in the variable section. ld/ * testsuite/ld-ctf/data-func-conflicted-vars.d: New test. libctf/ * ctf-link.c (ctf_link_deduplicating_variables): Duplicate symbols into the variable section too. * ctf-serialize.c (symtypetab_delete_nonstatic_vars): Rename to... (symtypetab_delete_nonstatics): ... this. Check the funchash when pruning redundant variables. (ctf_symtypetab_sect_sizes): Adjust accordingly. * NEWS: Describe this change.
Diffstat (limited to 'libctf/NEWS')
-rw-r--r--libctf/NEWS9
1 files changed, 9 insertions, 0 deletions
diff --git a/libctf/NEWS b/libctf/NEWS
index 956cca8..f4e5973 100644
--- a/libctf/NEWS
+++ b/libctf/NEWS
@@ -1,5 +1,14 @@
-*- text -*-
+Changes in 2.39:
+
+* New features
+
+** The CTF variable section (if generated via ld --ctf-variables) now contains
+ entries for static functions, hidden functions, and other functions with
+ no associated symbol. The associated type is of kind CTF_K_FUNCTION.
+ (No change if --ctf-variables is not specified, which is the default.)
+
Changes in 2.37:
* New features