summaryrefslogtreecommitdiff
path: root/bfd/aout-cris.c
diff options
context:
space:
mode:
authorHans-Peter Nilsson <hp@axis.com>2000-09-28 21:58:16 +0000
committerHans-Peter Nilsson <hp@axis.com>2000-09-28 21:58:16 +0000
commitf39e0726212947dca31cc12ed2891677773c6d7f (patch)
tree59a016c4e6599d099f1558940c63cc5f9f713f68 /bfd/aout-cris.c
parent82c51da5d5c45f4d8695c1431b6b1d12321945de (diff)
downloadbinutils-redhat-f39e0726212947dca31cc12ed2891677773c6d7f.tar.gz
* aout-cris.c (N_TXTADDR): Define.
Diffstat (limited to 'bfd/aout-cris.c')
-rw-r--r--bfd/aout-cris.c11
1 files changed, 11 insertions, 0 deletions
diff --git a/bfd/aout-cris.c b/bfd/aout-cris.c
index 36f8553369..a531bcbe97 100644
--- a/bfd/aout-cris.c
+++ b/bfd/aout-cris.c
@@ -28,6 +28,17 @@ Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. */
#define ENTRY_CAN_BE_ZERO
#define TEXT_START_ADDR 0
+/* Without reading symbols to get the text start symbol, there is no way
+ to know where the text segment starts in an a.out file. Defaulting to
+ anything as constant as TEXT_START_ADDR is bad. But we can guess from
+ the entry point, which is usually within the first 64k of the text
+ segment. We also assume here that the text segment is 64k-aligned.
+ FIXME: It is also wrong to assume that data and bss follow immediately
+ after text, but with those, we don't have any choice besides reading
+ symbol info, and luckily there's no pressing need for correctness for
+ those vma:s at this time. */
+#define N_TXTADDR(x) ((x).a_entry & ~0xffff)
+
/* If you change this to 4, you can not link to an address N*4+2. */
#define SEGMENT_SIZE 2