public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jj@sunsite.ms.mff.cuni.cz>
To: Richard Henderson <rth@cygnus.com>
Cc: ian@cygnus.com, binutils@sourceware.cygnus.com
Subject: [PATCH] My current SPARC patches
Date: Fri, 09 Jul 1999 05:40:00 -0000	[thread overview]
Message-ID: <19990709144003.K1736@mff.cuni.cz> (raw)
In-Reply-To: <19990708155013.A17592@cygnus.com>

On Thu, Jul 08, 1999 at 03:50:13PM -0700, Richard Henderson wrote:
> 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

That's because of the mips64 changes which went in two days ago after I
submited my patch. Below are all my current patches against current cvs
with the exception of the emulparams/elf64_sparc.sh.
> 
> These bits I went ahead and put in.

Thanks.

elf64-sparc.c was not compiling because it used DT_SPARC_PLTFMT, which is
now removed. This is the Diff-pltfmt patch.
ELF64_R_TYPE_DATA is always used on the whole r_info, so the macro has to
mask out ELF64_R_TYPE bits. This is the second patch,
Diff-elf64-r-type-data.
Then there is a c-sparc.texi update and then STT_REGISTER and R_SPARC_OLO10
patches.

Cheers,
    Jakub
___________________________________________________________________
Jakub Jelinek | jj@sunsite.mff.cuni.cz | http://sunsite.mff.cuni.cz
Administrator of SunSITE Czech Republic, MFF, Charles University
___________________________________________________________________
UltraLinux  |  http://ultra.linux.cz/  |  http://ultra.penguin.cz/
Linux version 2.2.10 on a sparc64 machine (1343.49 BogoMips)
___________________________________________________________________

  reply	other threads:[~1999-07-09  5:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-05  8:47 [PATCH] Support for R_SPARC_OLO10 relocations Jakub Jelinek
1999-07-08 15:50 ` Richard Henderson
1999-07-09  5:40   ` Jakub Jelinek [this message]
1999-07-16 14:34     ` [PATCH] My current SPARC patches 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=19990709144003.K1736@mff.cuni.cz \
    --to=jj@sunsite.ms.mff.cuni.cz \
    --cc=binutils@sourceware.cygnus.com \
    --cc=ian@cygnus.com \
    --cc=rth@cygnus.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).