From: Nick Clifton <nickc@redhat.com>
To: Rodney Brown <rbrown@bravurasolutions.com.au>
Cc: gdb-patches@sources.redhat.com, binutils@sources.redhat.com
Subject: Re: Patch to bfd/aix5ppc-core.c for gdb-6.3 with gcc 4 on AIX5.1
Date: Mon, 08 Aug 2005 12:28:00 -0000 [thread overview]
Message-ID: <42F7512A.3060308@redhat.com> (raw)
In-Reply-To: <4F3B985B8E683C45B8C5F76B7AAB5AE5258A78@EXCHANGE.bravurasolutions.local>
[-- Attachment #1: Type: text/plain, Size: 657 bytes --]
Hi Rodney,
> Are you using a gcc 4.1 development compiler?
Yes - but I am not compiling under AIX. I do not have access to an
AIX5.1 system, so when I built a cross compiler the build system must
have left out the core file support. Silly me.
> I assumed that using the accessor macro was the preferred mechanism.
It is, but when the macro is tied to a single particular function it
really ought to be defined inside the function. That way if the code is
ever rearranged it will not be lost.
So - what do you think of the attached, simplified patch ? If it fixes
the compile time warning then I would be happy to check it in.
Cheers
Nick
[-- Attachment #2: aix5.1ppc-core.c.patch --]
[-- Type: text/plain, Size: 1823 bytes --]
Index: bfd/aix5ppc-core.c
===================================================================
RCS file: /cvs/src/src/bfd/aix5ppc-core.c,v
retrieving revision 1.11
diff -c -3 -p -r1.11 aix5ppc-core.c
*** bfd/aix5ppc-core.c 18 Jul 2005 14:13:33 -0000 1.11
--- bfd/aix5ppc-core.c 8 Aug 2005 12:24:45 -0000
***************
*** 1,5 ****
/* IBM RS/6000 "XCOFF" back-end for BFD.
! Copyright 2001, 2002, 2003, 2004
Free Software Foundation, Inc.
Written by Tom Rix
Contributed by Red Hat Inc.
--- 1,5 ----
/* IBM RS/6000 "XCOFF" back-end for BFD.
! Copyright 2001, 2002, 2003, 2004, 2005
Free Software Foundation, Inc.
Written by Tom Rix
Contributed by Red Hat Inc.
*************** xcoff64_core_p (bfd *abfd)
*** 55,61 ****
bfd_vma ld_offset;
bfd_size_type i;
struct vm_infox vminfo;
! bfd_target *return_value = NULL;
/* Get the header. */
if (bfd_seek (abfd, 0, SEEK_SET) != 0)
--- 55,61 ----
bfd_vma ld_offset;
bfd_size_type i;
struct vm_infox vminfo;
! const bfd_target *return_value = NULL;
/* Get the header. */
if (bfd_seek (abfd, 0, SEEK_SET) != 0)
*************** xcoff64_core_p (bfd *abfd)
*** 111,117 ****
return return_value;
memcpy (new_core_hdr, &core, sizeof (struct core_dumpxx));
! core_hdr(abfd) = (char *)new_core_hdr;
/* .stack section. */
sec = bfd_make_section_anyway (abfd, ".stack");
--- 111,120 ----
return return_value;
memcpy (new_core_hdr, &core, sizeof (struct core_dumpxx));
! /* The core_hdr() macro is not used here because it would be
! casting the LHS of an assignment and some versions of gcc
! will generate a warning for this. */
! abfd->tdata.any = new_core_hdr;
/* .stack section. */
sec = bfd_make_section_anyway (abfd, ".stack");
next prev parent reply other threads:[~2005-08-08 12:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-03 2:25 Rodney Brown
2005-08-08 12:28 ` Nick Clifton [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-09 8:59 Rodney Brown
2005-08-09 16:37 ` Nick Clifton
2005-07-15 9:17 Rodney Brown
2005-08-02 10:59 ` 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=42F7512A.3060308@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=rbrown@bravurasolutions.com.au \
/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