* binutils/bfd patch for rs6000
@ 1998-09-24 13:27 David Edelsohn
0 siblings, 0 replies; only message in thread
From: David Edelsohn @ 1998-09-24 13:27 UTC (permalink / raw)
To: gas2
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;
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~1998-09-24 13:27 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1998-09-24 13:27 binutils/bfd patch for rs6000 David Edelsohn
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).