aboutsummaryrefslogtreecommitdiff
path: root/bfd
diff options
context:
space:
mode:
authorAlan Modra <amodra@gmail.com>2023-01-16 15:23:21 +1030
committerAlan Modra <amodra@gmail.com>2023-01-16 23:25:26 +1030
commit4a3ab0855d6bea672adc5bd58641173a59e57803 (patch)
treeb1b1297a8c3f67db77060c5475b753b69215cbb8 /bfd
parent5999477d92aecd9df5fb0b2f04c33b987a7db40c (diff)
downloadgdb-4a3ab0855d6bea672adc5bd58641173a59e57803.zip
gdb-4a3ab0855d6bea672adc5bd58641173a59e57803.tar.gz
gdb-4a3ab0855d6bea672adc5bd58641173a59e57803.tar.bz2
COFF CALC_ADDEND comment
Old COFF (and AOUT) targets have unusual relocation addends. * coffcode.h (<Reading relocations>): Describe COFF addends.
Diffstat (limited to 'bfd')
-rw-r--r--bfd/coffcode.h8
1 files changed, 8 insertions, 0 deletions
diff --git a/bfd/coffcode.h b/bfd/coffcode.h
index e952bd7..c4f7d19 100644
--- a/bfd/coffcode.h
+++ b/bfd/coffcode.h
@@ -5092,6 +5092,14 @@ SUBSUBSECTION
structure, in a back end specific way. For instance, the 386
uses the @code{r_type} to directly produce an index
into a howto table vector.
+
+ o Note that @code{arelent.addend} for COFF is often not what
+ most people understand as a relocation addend, but rather an
+ adjustment to the relocation addend stored in section contents
+ of relocatable object files. The value found in section
+ contents may also be confusing, depending on both symbol value
+ and addend somewhat similar to the field value for a
+ final-linked object. See @code{CALC_ADDEND}.
*/
#ifndef CALC_ADDEND