From: Andreas Schwab <schwab@suse.de>
To: James E Wilson <wilson@specifixinc.com>
Cc: Nick Clifton <nickc@redhat.com>, Ben Elliston <bje@au1.ibm.com>,
binutils@sources.redhat.com
Subject: Re: build failure for ia64 (due to -Werror)
Date: Sat, 19 Mar 2005 01:56:00 -0000 [thread overview]
Message-ID: <jek6o47akz.fsf@sykes.suse.de> (raw)
In-Reply-To: <20050318234920.GE21148@bubble.modra.org> (Alan Modra's message of "Sat, 19 Mar 2005 10:19:20 +1030")
Alan Modra <amodra@bigpond.net.au> writes:
> This only hides other more serious bugs in this function if bfd_vma is
> 32-bit. For instance,
>
> case IA64_OPND_IMMU64:
> hit_addr -= (long) hit_addr & 0x3;
> t0 = bfd_getl64 (hit_addr);
> t1 = bfd_getl64 (hit_addr + 8);
Ok, this is broken too. I've reviewed all uses of bfd_vma and came up
with this patch. I think that should cover all those problems. Maybe we
should even dump ia64_insn and use bfd_uint64_t throughout instead?
Andreas.
2005-03-19 Andreas Schwab <schwab@suse.de>
* elfxx-ia64.c (elfNN_ia64_relax_ldxmov): Change type of insn to
ia64_insn and type of dword to bfd_uint64_t.
(elfNN_ia64_install_value): Change type of t0, t1 and dword to
bfd_uint64_t.
(elfNN_ia64_unwind_entry_compare): Change type of av and bv to
bfd_uint64_t.
Index: bfd/elfxx-ia64.c
===================================================================
RCS file: /cvs/src/src/bfd/elfxx-ia64.c,v
retrieving revision 1.150
diff -u -a -p -a -u -p -r1.150 bfd/elfxx-ia64.c
--- bfd/elfxx-ia64.c 18 Mar 2005 21:31:31 -0000 1.150
+++ bfd/elfxx-ia64.c 19 Mar 2005 00:14:10 -0000
@@ -1213,7 +1213,8 @@ elfNN_ia64_relax_ldxmov (contents, off)
bfd_vma off;
{
int shift, r1, r3;
- bfd_vma dword, insn;
+ ia64_insn insn;
+ bfd_uint64_t dword;
switch ((int)off & 0x3)
{
@@ -3119,7 +3120,7 @@ elfNN_ia64_install_value (hit_addr, v, r
{
const struct ia64_operand *op;
int bigendian = 0, shift = 0;
- bfd_vma t0, t1, dword;
+ bfd_uint64_t t0, t1, dword;
ia64_insn insn;
enum ia64_opnd opnd;
const char *err;
@@ -3652,7 +3653,7 @@ elfNN_ia64_unwind_entry_compare (a, b)
const PTR a;
const PTR b;
{
- bfd_vma av, bv;
+ bfd_uint64_t av, bv;
av = bfd_get_64 (elfNN_ia64_unwind_entry_compare_bfd, a);
bv = bfd_get_64 (elfNN_ia64_unwind_entry_compare_bfd, b);
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, MaxfeldstraÃe 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2005-03-19 0:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-18 3:58 Ben Elliston
2005-03-18 13:14 ` Nick Clifton
2005-03-18 14:13 ` Alan Modra
2005-03-18 22:15 ` James E Wilson
2005-03-18 22:49 ` Ian Lance Taylor
2005-03-18 23:31 ` Ian Lance Taylor
2005-03-18 23:52 ` James E Wilson
2005-03-18 23:37 ` Andreas Schwab
2005-03-19 0:42 ` Alan Modra
2005-03-19 1:56 ` Andreas Schwab [this message]
2005-03-19 4:04 ` James E Wilson
2005-03-19 4:30 ` Andreas Schwab
2005-03-19 9:44 ` James E Wilson
2005-03-19 12:13 ` James E Wilson
2005-03-19 17:57 ` James E Wilson
2005-03-19 18:37 ` Alan Modra
2005-03-19 18:33 ` James E Wilson
2005-03-19 19:00 ` Andreas Schwab
2005-03-23 9:45 ` James E Wilson
2005-03-23 19:24 ` Nick Clifton
2005-03-24 9:27 ` James E Wilson
2005-03-24 14:58 ` Nick Clifton
2005-03-19 0:56 ` Alan Modra
2005-03-22 2:19 ` Ben Elliston
2005-03-20 9:26 Paul Schlie
2005-03-20 19:42 ` Andreas Schwab
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=jek6o47akz.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=binutils@sources.redhat.com \
--cc=bje@au1.ibm.com \
--cc=nickc@redhat.com \
--cc=wilson@specifixinc.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).