Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Ulrich Weigand <uweigand@de.ibm.com>, gdb-patches@sourceware.org
Subject: Re: [rfc/rft] ppc gdbserver: autodetect AltiVec and SPE
Date: Sun, 20 Apr 2008 14:28:00 -0000	[thread overview]
Message-ID: <1208667119.5808.126.camel@localhost.localdomain> (raw)
In-Reply-To: <20080419035837.GB22517@caradoc.them.org>

On Fri, 2008-04-18 at 23:58 -0400, Daniel Jacobowitz wrote:
> On Fri, Apr 18, 2008 at 09:07:25PM -0300, Thiago Jung Bauermann wrote:
> > gdbserver is not compiling anymore on Linux/ppc. I believe this patch is
> > the cause:
> > 
> > gcc -Wall -g -O2    -I. -I../../../gdb.hg/gdb/gdbserver -I../../../gdb.hg/gdb/gdbserver/../regformats -I../../../gdb.hg/gdb/gdbserver/../../include -I../../bfd -I../../../gdb.hg/gdb/gdbserver/../../bfd  -rdynamic -o gdbserver inferiors.o regcache.o remote-utils.o server.o signals.o target.o utils.o version.o mem-break.o hostio.o xml-builtin.o reg-ppc.o powerpc-32.o reg-ppc64.o powerpc-64.o linux-low.o linux-ppc-low.o hostio-errno.o thread-db.o proc-service.o  \
> >   -lthread_db
> > linux-ppc-low.o: In function `ppc_arch_setup':
> > ../../../gdb.hg/gdb/gdbserver/linux-ppc-low.c:255: undefined reference to `init_registers_powerpc_e500'
> > collect2: ld returned 1 exit status
> > make[4]: *** [gdbserver] Error 1
> > make[4]: Leaving directory `/home/bauermann/tmp/remove-dead-fn/build/gdb/gdbserver'
> 
> Looks like you have to rerun configure.  Maybe a missing dependency
> somewhere (Makefile on configure.srv?).

No, it was a clean build. I got what's happening. The patch removed
powerpc-e500.o from powerpc64-*-linux*, because e500 is 32-bit only. The
call to init_registers_powerpc_e500 is protected by an #ifndef
__powerpc64__, so it shouldn't be a problem. But in practice it is,
because when using plain "../src/configure && make" in a ppc64 machine
with a 32-bit default gcc, the target is autodetected to be
powerpc64-unknown-linux-gnu. Thus, that call to
init_registers_powerpc_e500 will be compiled in (it's a 32 bit
compilation), but powerpc-e500.o won't be included (it's a powerpc64
target).

Is such way of compiling 32-bit GDB in a ppc64 machine with 32-bit
default gcc not supported? Must one always use --target option to
configure in such case?
-- 
[]'s
Thiago Jung Bauermann
Software Engineer
IBM Linux Technology Center


  reply	other threads:[~2008-04-20  4:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-08  1:11 [rfc][3/3] gdbserver bi-arch for ppc: enable bi-arch support Ulrich Weigand
2008-02-27 13:20 ` Daniel Jacobowitz
2008-02-28  7:16   ` Ulrich Weigand
2008-02-28 14:13     ` Daniel Jacobowitz
2008-02-28 17:03       ` [rfc/rft] ppc gdbserver: autodetect AltiVec and SPE Ulrich Weigand
2008-02-28 17:12         ` Daniel Jacobowitz
2008-03-26 20:21           ` Ulrich Weigand
2008-04-19  0:19             ` Thiago Jung Bauermann
2008-04-19  6:17               ` Daniel Jacobowitz
2008-04-20 14:28                 ` Thiago Jung Bauermann [this message]
2008-04-21  9:21                   ` Daniel Jacobowitz
2008-04-21 10:00                     ` Thiago Jung Bauermann
2008-04-21 14:04                       ` Ulrich Weigand
2008-04-21 14:32                         ` Daniel Jacobowitz
2008-04-21 15:36                           ` Ulrich Weigand
2008-04-21 15:38                             ` Daniel Jacobowitz
2008-04-17 17:47         ` Daniel Jacobowitz
2008-04-17 19:03           ` Daniel Jacobowitz
2008-04-17 21:34             ` Ulrich Weigand

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=1208667119.5808.126.camel@localhost.localdomain \
    --to=bauerman@br.ibm.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=uweigand@de.ibm.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