From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] gas generates incorrect ia64 unwind rlen values
Date: Mon, 16 Dec 2002 22:11:21 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805577@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805566@msgid-missing>
>>>>> On Mon, 16 Dec 2002 15:46:27 +1100, Keith Owens <kaos@sgi.com> said:
Keith> As I mentioned in the previous mail, I could not find any mail, bug
Keith> reports or changelog entries that mentioned ia64 unwind or rlen being
Keith> wrong. Which makes me think that the bug exists in current binutils,
Keith> however I cannot test that at the moment.
Trust me: there were at least 2 or 3 fixes; some in the compiler, some
in binutils. Here is an example from gas:
2002-02-22 David Mosberger <davidm@hpl.hp.com>
* config/tc-ia64.c (dot_restore): Issue error message of epilogue
count exceeds prologue count.
(md_show_usage): Describe -mconstant-gp and -mauto-pic.
(unwind.label_prologue_count): New member.
Based on a patch by Hans Boehm <hboehm@hpl.hp.com>:
(get_saved_prologue_count): New function.
(save_prologue_count): New function.
(free_saved_prologue_count): New function.
(dot_label_state): Record state label by calling save_prologue_count().
(dot_copy_state): Restore prologue count by calling
get_saved_prologue_count().
(generate_unwind_image): Free up list of saved prologue
counts by calling free_saved_prologue_counts().
--david
prev parent reply other threads:[~2002-12-16 22:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-16 1:24 [Linux-ia64] gas generates incorrect ia64 unwind rlen values Keith Owens
2002-12-16 3:38 ` Grant Grundler
2002-12-16 4:46 ` Keith Owens
2002-12-16 21:25 ` Jim Wilson
2002-12-16 22:08 ` David Mosberger
2002-12-16 22:11 ` David Mosberger [this message]
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-105590709805577@msgid-missing \
--to=davidm@napali.hpl.hp.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.