From: Alan Modra <amodra@gmail.com>
To: binutils@sourceware.org
Subject: COFF CALC_ADDEND comment
Date: Mon, 16 Jan 2023 23:24:33 +1030 [thread overview]
Message-ID: <Y8VJCZte0qnkPRWk@squeak.grove.modra.org> (raw)
Old COFF (and AOUT) targets have unusual relocation addends.
* coffcode.h (<Reading relocations>): Describe COFF addends.
diff --git a/bfd/coffcode.h b/bfd/coffcode.h
index e952bd77d6a..168bb8a55c2 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
--
Alan Modra
Australia Development Lab, IBM
reply other threads:[~2023-01-16 12:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y8VJCZte0qnkPRWk@squeak.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).