From: "H. J. Lu" <hjl@lucon.org>
To: linux-kernel@vger.kernel.org,
David Mosberger <davidm@napali.hpl.hp.com>,
"Luck, Tony" <tony.luck@intel.com>,
gcc@gcc.gnu.org, GNU C Library <libc-alpha@sources.redhat.com>
Subject: Re: binutils 2.15.90.0.1 break ia64 kernel crosscompiling
Date: Fri, 5 Mar 2004 09:08:32 -0800 [thread overview]
Message-ID: <20040305170832.GA16182@lucon.org> (raw)
In-Reply-To: <20040305142725.GA20926@MAIL.13thfloor.at>
On Fri, Mar 05, 2004 at 03:27:25PM +0100, Herbert Poetzl wrote:
>
> Hi Folks!
>
> upgraded my Cross Compiling Toolchain[1] to binutils 2.15.90.0.1,
> recompiled gcc 3.3.3 (just to make sure), and now linux 2.6.3
> doesn't compile for ia64 anymore ...
>
> here is th funny part of the complete error log[2]
>
> ------------------------------------------------------------------
> {standard input}: Assembler messages:
> {standard input}:1268: Internal error!
> Assertion failure in md_assemble at config/tc-ia64.c line 10013.
> Please report this bug.
> ------------------------------------------------------------------
>
> so we are now down from 6 to 5 of 20 archs which compile 2.6.3
> with default config, will soon try with 2.6.4-rc*
>
I checked in this patch. Please test it as much as you can on ia64.
H.J.
----
2004-03-04 H.J. Lu <hongjiu.lu@intel.com>
* config/tc-ia64.c (md_assemble): Properly handle NULL
align_frag.
(ia64_handle_align): Don't abort if failed to add a stop bit.
--- gas/config/tc-ia64.c.align 2004-03-03 11:49:14.000000000 -0800
+++ gas/config/tc-ia64.c 2004-03-04 15:19:37.000000000 -0800
@@ -10010,9 +10010,12 @@ md_assemble (str)
while (align_frag->fr_type != rs_align_code)
{
align_frag = align_frag->fr_next;
- assert (align_frag);
+ if (!align_frag)
+ break;
}
- if (align_frag->fr_next == frag_now)
+ /* align_frag can be NULL if there are directives in
+ between. */
+ if (align_frag && align_frag->fr_next == frag_now)
align_frag->tc_frag_data = 1;
}
@@ -10872,8 +10875,16 @@ ia64_handle_align (fragp)
if (!bytes && fragp->tc_frag_data)
{
if (fragp->fr_fix < 16)
+#if 1
+ /* FIXME: It won't work with
+ .align 16
+ alloc r32=ar.pfs,1,2,4,0
+ */
+ ;
+#else
as_bad_where (fragp->fr_file, fragp->fr_line,
_("Can't add stop bit to mark end of instruction group"));
+#endif
else
/* Bundles are always in little-endian byte order. Make sure
the previous bundle has the stop bit. */
next prev parent reply other threads:[~2004-03-05 17:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-05 14:27 binutils 2.15.90.0.1 break ia64 kernel crosscompiling Herbert Poetzl
2004-03-05 16:50 ` H. J. Lu
2004-03-05 17:08 ` H. J. Lu [this message]
[not found] <1woEF-7Yx-7@gated-at.bofh.it>
2004-03-05 14:52 ` Pascal Schmidt
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=20040305170832.GA16182@lucon.org \
--to=hjl@lucon.org \
--cc=davidm@napali.hpl.hp.com \
--cc=gcc@gcc.gnu.org \
--cc=libc-alpha@sources.redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
/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