From: Andreas Schwab <schwab@suse.de>
To: Jason Eckhardt <jle@cygnus.com>
Cc: binutils@sourceware.cygnus.com
Subject: Re: [patch] bfd, new bfd_relocs for i860
Date: Mon, 31 Jul 2000 04:35:00 -0000 [thread overview]
Message-ID: <200007311135.NAA10259@hawking.suse.de> (raw)
In-Reply-To: <Pine.SOL.3.91.1000730143408.4267A@cse.cygnus.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1210 bytes --]
Jason Eckhardt <jle@cygnus.com> writes:
|> These are new BFD_RELOC_*'s for i860.
|>
|> Are bfd-in2.h and libbfd.h the only regens I need to do for a change to
|> reloc.c?
|>
|> 2000-07-30 Jason Eckhardt <jle@cygnus.com>
|>
|> * bfd/reloc.c (BFD_RELOC_860_*): New bfd relocs for i860.
|> * bfd/bfd-in2.h, libbfd.h: Regenerate.
|>
|>
|> Index: bfd/reloc.c
|> ===================================================================
|> RCS file: /cvs/src/src/bfd/reloc.c,v
|> retrieving revision 1.27
|> diff -c -3 -p -r1.27 reloc.c
|> *** reloc.c 2000/07/20 16:21:07 1.27
|> --- reloc.c 2000/07/30 21:32:21
|> *************** ENUMDOC
|> *** 2912,2917 ****
|> --- 2912,2988 ----
|> These relocs are only used within the CRIS assembler. They are not
|> (at present) written to any object files.
|>
|> + ENUM
|> + BFD_RELOC_860_NONE
|> + ENUMX
|> + BFD_RELOC_860_32
In which way are these different from BFD_RELOC_NONE and BFD_RELOC_32,
resp.?
Andreas.
--
Andreas Schwab "And now for something
SuSE Labs completely different."
Andreas.Schwab@suse.de
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
next prev parent reply other threads:[~2000-07-31 4:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-30 14:36 Jason Eckhardt
2000-07-31 4:35 ` Andreas Schwab [this message]
2000-07-31 8:40 ` Jason Eckhardt
2000-07-31 15:17 Nick Clifton
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=200007311135.NAA10259@hawking.suse.de \
--to=schwab@suse.de \
--cc=binutils@sourceware.cygnus.com \
--cc=jle@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).