public inbox for gas2@sourceware.org
 help / color / mirror / Atom feed
From: David Edelsohn <dje@watson.ibm.com>
To: gas2@cygnus.com
Subject: binutils/bfd patch for rs6000
Date: Thu, 24 Sep 1998 13:27:00 -0000	[thread overview]
Message-ID: <9809242027.AA33404@marc.watson.ibm.com> (raw)

	Sorry if this is the wrong list to send this to; I'm not sure if
there is a bfd-specific mailinglist now.

	While doing some preliminary exploration of adding AIX 4.3 64-bit
support to BFD, we ran across some minor bugs when simply configuring BFD
for 64-bit operation with --enable-64-bit-bfd.  Configured this way,
binutils creates a broken version of objdump and other utilities because
some variables which other parts of bfd now declare as "bfd_size_type"
still are declared as "int" within rs6000-core.  Note that this has
nothing to do with the ability to read/write 64-bit executables, just with
the ability to use 64-bit fields internally while reading/writing 32-bit
executables.

David


Thu Sep 24 16:15:13 1998  David Edelsohn  <edelsohn@mhpcc.edu>

	* rs6000-core.c (rs6000coff_core_file_matches_executable_p):
	Declare size as bfd_size_type.
	(rs6000coff_get_section_contents): Declare count as bfd_size_type. 

*** rs6000-core.c~	Wed Sep  9 09:24:00 1998
--- rs6000-core.c	Mon Sep 14 17:30:25 1998
***************
*** 361,367 ****
  {
    struct core_dump coredata;
    struct ld_info ldinfo;
!   int size;
    char *path, *s;
    size_t alloc;
    const char *str1, *str2;
--- 361,367 ----
  {
    struct core_dump coredata;
    struct ld_info ldinfo;
!   bfd_size_type size;
    char *path, *s;
    size_t alloc;
    const char *str1, *str2;
***************
*** 452,458 ****
       sec_ptr section;
       PTR location;
       file_ptr offset;
!      int count;
  {
      if (count == 0)
  	return true;
--- 452,458 ----
       sec_ptr section;
       PTR location;
       file_ptr offset;
!      bfd_size_type count;
  {
      if (count == 0)
  	return true;

                 reply	other threads:[~1998-09-24 13:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=9809242027.AA33404@marc.watson.ibm.com \
    --to=dje@watson.ibm.com \
    --cc=gas2@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).