diff options
| author | Andrew Burgess <andrew.burgess@embecosm.com> | 2018-01-05 22:41:55 +0000 |
|---|---|---|
| committer | Andrew Burgess <andrew.burgess@embecosm.com> | 2018-01-11 17:33:20 +0000 |
| commit | b3b9f8d3e99cf46c2f85445cc5189db4c4f47407 (patch) | |
| tree | 6ef8b5b71229cc38a7fe99ad971693f6f1ffac4f /ld/ChangeLog | |
| parent | 6bd0a312a4cb6803b9d6aa2f5646b610d213a1fe (diff) | |
| download | gdb-b3b9f8d3e99cf46c2f85445cc5189db4c4f47407.zip gdb-b3b9f8d3e99cf46c2f85445cc5189db4c4f47407.tar.gz gdb-b3b9f8d3e99cf46c2f85445cc5189db4c4f47407.tar.bz2 | |
ld: In map file use '=' in PROVIDE statements
Currently when recording a PROVIDE statement in a linker map file we
display something like:
PROVIDE (SYMBOL, VALUE)
However, in a linker script we write these statements like this:
PROVIDE (SYMBOL = VALUE);
This commit changes the output in the map file to be closer to linker
script format, the map file now contains:
PROVIDE (SYMBOL = VALUE)
The ';' is still missing from the end, but map files are not intended
to be valid linker script input, so adding the ';' just seems like
clutter.
ld/ChangeLog:
* ldexp.c (exp_print_tree): Use '=' instead of ',' when printing
PROVIDE statements.
* testsuite/ld-scripts/provide-4.map: Update expected output.
* testsuite/ld-scripts/provide-5.map: Likewise.
Diffstat (limited to 'ld/ChangeLog')
| -rw-r--r-- | ld/ChangeLog | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/ld/ChangeLog b/ld/ChangeLog index c5085b1..1357b89 100644 --- a/ld/ChangeLog +++ b/ld/ChangeLog @@ -1,3 +1,10 @@ +2018-01-11 Andrew Burgess <andrew.burgess@embecosm.com> + + * ldexp.c (exp_print_tree): Use '=' instead of ',' when printing + PROVIDE statements. + * testsuite/ld-scripts/provide-4.map: Update expected output. + * testsuite/ld-scripts/provide-5.map: Likewise. + 2018-01-11 H.J. Lu <hongjiu.lu@intel.com> PR ld/22696 |