From: Paul Gilliam <pgilliam@us.ibm.com>
To: gdb@sources.redhat.com
Subject: Re: Problem building GDB on Power64
Date: Thu, 02 Sep 2004 17:54:00 -0000 [thread overview]
Message-ID: <200409021052.04994.pgilliam@us.ibm.com> (raw)
In-Reply-To: <20040902172158.GA15192@nevyn.them.org>
On Thursday 02 September 2004 10:21, Daniel Jacobowitz wrote:
> On Thu, Sep 02, 2004 at 09:20:53AM -0700, Paul Gilliam wrote:
> > On a ppc64 system, GDB builds as a 32-bit application. This is OK if the
> > 64-bit dev. env. is not available. But if it is, this is wrong: GDB
> > should build as a 64-bit application so that both 64 and 32 bit apps can
> > be debugged.
> >
> > If I understood the configure process, I would have tried submitting a
> > patch. It should be easy: just include -m64 in the CFLAGS. And make sure
> > to link with the 64-bit libraries (which had better be there).
>
> IMO, if your 64-bit environment defaults to building 32-bit code, it's
> your responsibility to set -m64 yourself.
Normally I would agree with you, but this is kind of a special case.
The reason the 64-bit environment defaults to building 32-bit code is that it
was felt that most applications running on a 64-bit processor will be 32-bit
applications. (at least that's what the gcc person in the next cube explained
to me).
But, if possible, the debugger should handle either. In fact, the gdb
installed with the 64-bit dev. system is a 64-bit app. and can debug both 64
and 32 bit apps.
In this case, then, I think it makes more sense for gdb to build atomaticly as
a 64-bit app, if it can be.
-=# Paul #=-
PS: I'm not asking for someone to post patches to configure.in or what ever,
(hinting maybe), but I am asking for some pointers on where to look.
next prev parent reply other threads:[~2004-09-02 17:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-02 16:23 Paul Gilliam
2004-09-02 17:22 ` Daniel Jacobowitz
2004-09-02 17:54 ` Paul Gilliam [this message]
2004-09-02 17:59 ` Daniel Jacobowitz
2004-09-02 18:51 ` Andrew Cagney
2004-09-02 20:17 ` Michael Chastain
2004-09-02 20:30 ` Eli Zaretskii
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=200409021052.04994.pgilliam@us.ibm.com \
--to=pgilliam@us.ibm.com \
--cc=gdb@sources.redhat.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