From: Jim Wilson <wilson@cygnus.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] 001117 toolchain release
Date: Wed, 22 Nov 2000 02:18:50 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205762@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205748@msgid-missing>
Why 16 bytes? The sections only have 8 byte data. (Technically, the unwind
section has 4 byte data for the 32-bit ABI, but I'm ignoring that for now.)
I added this patch to the FSF binutils sources to fix the problem. I am not
planning to add a patch for the 001117 release, since this doesn't seem to
be a serious enough problem.
2000-11-21 Jim Wilson <wilson@redhat.com>
* config/tc-ia64.c (generate_unwind_image): Call record_alignment
for unwind info section.
(dot_endp): Likewise for unwind section.
Index: tc-ia64.c
=================================RCS file: /cvs/src/src/gas/config/tc-ia64.c,v
retrieving revision 1.33
diff -p -r1.33 tc-ia64.c
*** tc-ia64.c 2000/11/22 01:12:05 1.33
--- tc-ia64.c 2000/11/22 02:01:42
*************** generate_unwind_image ()
*** 3057,3062 ****
--- 3057,3065 ----
expressionS exp;
set_section ((char *) special_section_name[SPECIAL_SECTION_UNWIND_INFO]);
+ /* Make sure the section has 8 byte alignment. */
+ record_alignment (now_seg, 3);
+
/* Set expression which points to start of unwind descriptor area. */
unwind.info = expr_build_dot ();
*************** dot_endp (dummy)
*** 3684,3689 ****
--- 3687,3696 ----
unwind.proc_end = expr_build_dot ();
set_section ((char *) special_section_name[SPECIAL_SECTION_UNWIND]);
+
+ /* Make sure the section has 8 byte alignment. */
+ record_alignment (now_seg, 3);
+
ptr = frag_more (24);
where = frag_now_fix () - 24;
bytes_per_address = bfd_arch_bits_per_address (stdoutput) / 8;
next prev parent reply other threads:[~2000-11-22 2:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-18 5:34 [Linux-ia64] 001117 toolchain release Jim Wilson
2000-11-21 5:47 ` Keith Owens
2000-11-22 2:18 ` Jim Wilson [this message]
2000-11-22 2:33 ` Keith Owens
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=marc-linux-ia64-105590678205762@msgid-missing \
--to=wilson@cygnus.com \
--cc=linux-ia64@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.