Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: "Roberts, Dennis" <Dennis.Roberts@sunquestinfo.com>
Cc: "'gdb-patches@sourceware.org'" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix for 64-Bit Core Files on AIX
Date: Wed, 16 Apr 2008 21:34:00 -0000	[thread overview]
Message-ID: <20080416211607.GD3631@adacore.com> (raw)
In-Reply-To: <4813EA4A50D35A44906A74A5E341D0B61A03388643@SQMAILBOX1.sunquestinfo.com>

Dennis,

> 2008-04-15  Dennis Roberts  <dennis.roberts@sunquestinfo.com>
> 
> 	* rs6000-tdep.c (rs6000_gdbarch_init): Use the BFD architecture,
> 	rather than a hard-coded architecture, for xcoff executables.

I have reviewed the change, and it looks OK (and can be applied
independently of the BFD part). But I just wanted to make sure that
you have indeed tested this change both in 32 and 64 bit modes.
Is that correct?  

The change is sufficiently small that it qualifies as a non-legally
significant change (patch repeated at the end of this email for quick
reference), but if you think you are going to make more contributions,
I would encourage you to provide a copyright assignment to the FSF.
We could then offer you write access to the repository.  I can help you
get started if you like.

In the meantime, I will commit your change as soon as you have confirmed
testing.

Thank you,
-- 
Joel

> diff -rc src.orig/gdb/rs6000-tdep.c src/gdb/rs6000-tdep.c
> *** src.orig/gdb/rs6000-tdep.c	Wed Feb 20 07:34:43 2008
> --- src/gdb/rs6000-tdep.c	Tue Apr 15 13:33:10 2008
> ***************
> *** 3307,3324 ****
>   	wordsize = 4;
>       }
>   
> !   if (!from_xcoff_exec)
> !     {
> !       arch = info.bfd_arch_info->arch;
> !       mach = info.bfd_arch_info->mach;
> !     }
> !   else
> !     {
> !       arch = bfd_arch_powerpc;
> !       bfd_default_set_arch_mach (&abfd, arch, 0);
> !       info.bfd_arch_info = bfd_get_arch_info (&abfd);
> !       mach = info.bfd_arch_info->mach;
> !     }
>   
>     /* For e500 executables, the apuinfo section is of help here.  Such
>        section contains the identifier and revision number of each
> --- 3307,3315 ----
>   	wordsize = 4;
>       }
>   
> !   /* Get the architecture and machine from the BFD. */
> !   arch = info.bfd_arch_info->arch;
> !   mach = info.bfd_arch_info->mach;
>   
>     /* For e500 executables, the apuinfo section is of help here.  Such
>        section contains the identifier and revision number of each


  reply	other threads:[~2008-04-16 21:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-16  8:12 Roberts, Dennis
2008-04-16 21:34 ` Joel Brobecker [this message]
2008-04-16 21:55   ` Roberts, Dennis
2008-04-16 22:25     ` Joel Brobecker
2008-04-16 22:40       ` Roberts, Dennis
2008-04-17 21:16       ` Joel Brobecker
2008-04-17 21:25         ` Roberts, Dennis
2008-04-18 18:48         ` Roberts, Dennis
2008-04-19  1:26           ` Joel Brobecker

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=20080416211607.GD3631@adacore.com \
    --to=brobecker@adacore.com \
    --cc=Dennis.Roberts@sunquestinfo.com \
    --cc=gdb-patches@sourceware.org \
    /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