summaryrefslogtreecommitdiff
path: root/ld/ld.texinfo
diff options
context:
space:
mode:
authorNick Clifton <nickc@redhat.com>2001-09-24 16:17:46 +0000
committerNick Clifton <nickc@redhat.com>2001-09-24 16:17:46 +0000
commit761926ad25c7d446980271e440013ff7a1f958e7 (patch)
tree752ae4ff8a1740e933031c0403ea5b1b5f8e53ce /ld/ld.texinfo
parent0514bbb4184bbd5353f34d0b65c135ff2c23b651 (diff)
downloadbinutils-redhat-761926ad25c7d446980271e440013ff7a1f958e7.tar.gz
improve documenation about auto-import
Diffstat (limited to 'ld/ld.texinfo')
-rw-r--r--ld/ld.texinfo13
1 files changed, 10 insertions, 3 deletions
diff --git a/ld/ld.texinfo b/ld/ld.texinfo
index 209875c7b0..fd03bc3e9b 100644
--- a/ld/ld.texinfo
+++ b/ld/ld.texinfo
@@ -1738,8 +1738,14 @@ This message occurs when some (sub)expression accesses an address
ultimately given by the sum of two constants (Win32 import tables only
allow one). Instances where this may occur include accesses to member
fields of struct variables imported from a DLL, as well as using a
-constant index into an array variable imported from a DLL. There are
-several ways to address this difficulty.
+constant index into an array variable imported from a DLL. Any
+multiword variable (arrays, structs, long long, etc) may trigger
+this error condition. However, regardless of the exact data type
+of the offending exported variable, ld will always detect it, issue
+the warning, and exit.
+
+There are several ways to address this difficulty, regardless of the
+data type of the exported variable:
One solution is to force one of the 'constants' to be a variable --
that is, unknown and un-optimizable at compile time. For arrays,
@@ -1760,7 +1766,8 @@ extern_array[1] -->
@{ volatile int t=1; extern_array[t] @}
@end example
-For structs, the only option is to make the struct itself variable:
+For structs (and most other multiword data types) the only option
+is to make the struct itself (or the long long, or the ...) variable:
@example
extern struct s extern_struct;