From: Richard Henderson <rth@cygnus.com>
To: Jakub Jelinek <jj@sunsite.ms.mff.cuni.cz>
Cc: binutils@sourceware.cygnus.com
Subject: Re: [PATCH] Support for R_SPARC_OLO10 relocations
Date: Thu, 08 Jul 1999 15:50:00 -0000 [thread overview]
Message-ID: <19990708155013.A17592@cygnus.com> (raw)
In-Reply-To: <19990705174729.B1736@mff.cuni.cz>
On Mon, Jul 05, 1999 at 05:47:29PM +0200, Jakub Jelinek wrote:
> This patch adds support for R_SPARC_OLO10 relocation.
I'm getting errors compiling this code.
gcc -DHAVE_CONFIG_H -I. -I../../../binutils/bfd -I. -D_GNU_SOURCE -I. -I../../..
/binutils/bfd -I../../../binutils/bfd/../include -I../../../binutils/bfd/../intl
-I../intl -g -O2 -c ../../../binutils/bfd/elf64-sparc.c -o elf64-sparc.o
.../elf64-sparc.c:2636: warning: initialization makes integer from pointer without a cast
.../elf64-sparc.c:2636: initializer element is not computable at load time
.../elf64-sparc.c:2636: (near initialization for `sparc64_elf_size_info.elfclass')
.../elf64-sparc.c:2637: warning: initialization makes integer from pointer without a cast
.../elf64-sparc.c:2637: initializer element is not computable at load time
...elf64-sparc.c:2637: (near initialization for `sparc64_elf_size_info.ev_current')
.../elf64-sparc.c:2638: warning: initialization from incompatible pointer type
.../elf64-sparc.c:2639: warning: initialization from incompatible pointer type
.../elf64-sparc.c:2640: warning: initialization from incompatible pointer type
.../elf64-sparc.c:2641: warning: initialization from incompatible pointer type
.../elf64-sparc.c:2643: warning: initialization from incompatible pointer type
Would you please update from cvs and make a new patch?
> * binutils/readelf.c (guess_is_rela): Sparcv9 and v8plus use rela.
> (dump_relocations): Use ELF64_R_TYPE_ID for Sparc, for R_SPARC_OLO10
> print the secondary addend.
> (get_machine_flags): Print Sparc machine flags.
> (get_symbol_type): Print STT_REGISTER.
> * include/elf/sparc.h (ELF64_R_TYPE_DATA): Sign extend the value.
> (ELF64_R_TYPE_INFO): Mask out all but low 24 bits of data.
> * opcodes/sparc-dis.c (print_insn_sparc): Differentiate between
> addition and oring when guessing symbol for comment.
These bits I went ahead and put in.
r~
next prev parent reply other threads:[~1999-07-08 15:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-05 8:47 Jakub Jelinek
1999-07-08 15:50 ` Richard Henderson [this message]
1999-07-09 5:40 ` [PATCH] My current SPARC patches Jakub Jelinek
1999-07-16 14:34 ` Richard Henderson
1999-07-08 16:09 ` [PATCH] Support for R_SPARC_OLO10 relocations Richard Henderson
1999-07-08 20:02 ` Ian Lance Taylor
1999-07-08 23:34 ` Jakub Jelinek
1999-07-09 9:52 ` Ian Lance Taylor
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=19990708155013.A17592@cygnus.com \
--to=rth@cygnus.com \
--cc=binutils@sourceware.cygnus.com \
--cc=jj@sunsite.ms.mff.cuni.cz \
/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).