public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "H. J. Lu" <hjl@lucon.org>
To: rth@redhat.com
Cc: binutils@sources.redhat.com
Subject: IA64 linker is broken
Date: Tue, 04 Mar 2003 20:13:00 -0000	[thread overview]
Message-ID: <20030304121322.A30843@lucon.org> (raw)

Hi Richard,

You added a call to get_dyn_sym_info in your last change without checking
relocation type. Now

--foo.s--
        .section .text
 {   .mib
        nop.m   0
        nop.i   0
        br.cond.dpnt.many       .b1_1 ;;
 }
        .section .text1
 .b1_1:
 {   .mii
        nop.m   0
        nop.i   0
        nop.i   0
 }
----

No longer works. You may want to check the relocation type first.


H.J.

             reply	other threads:[~2003-03-04 20:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-04 20:13 H. J. Lu [this message]
2003-03-18 15:25 ` [PATCH] " Jakub Jelinek
2003-03-18 18:57   ` Richard Henderson
2005-01-30 19:22 H. J. Lu
2005-01-31  0:02 ` Alan Modra
2005-01-31  7:13   ` Alan Modra
2005-01-31  8:29     ` Alan Modra
2005-01-31 18:38       ` H. J. Lu
2005-02-01  1:41     ` Alan Modra

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=20030304121322.A30843@lucon.org \
    --to=hjl@lucon.org \
    --cc=binutils@sources.redhat.com \
    --cc=rth@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).