From: Daniel Jacobowitz <drow@mvista.com>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: Will Schmidt <willschm@us.ibm.com>,
gdb-patches@sources.redhat.com, will_schmidt@vnet.ibm.com
Subject: Re: [PATCH] new support for PPC64 architecture
Date: Wed, 07 May 2003 20:46:00 -0000 [thread overview]
Message-ID: <20030507204601.GA25740@nevyn.them.org> (raw)
In-Reply-To: <16057.28595.975866.87959@localhost.redhat.com>
On Wed, May 07, 2003 at 04:42:27PM -0400, Elena Zannoni wrote:
> Will Schmidt writes:
> > All,
> >
> > This patch contains code that provides support for GDB on the PPC64
> > architecture. This patch will apply clean on top of the RedHat
> > gdb-5.3post-0.20021129.29.src.rpm. (A patch against CVS will
> > happen, but not today.. )
> >
> >
> > (See attached file: gdb-5.3post-ppc64-support.patch)
> >
> >
> > -Will
> >
> >
> > Will Schmidt
> > willschm@us.ibm.com will_schmidt@vnet.ibm.com
> > Linux on PowerPC-64 Development
> > IBM Rochester
>
> A few comments/questions. You need changelogs, and the proper
> copyright verbiage in the new files you are adding. The code needs to
> conform to gnu coding standards as fas as spaces, indentation,
> etc. You can run the new files through gdb_indent.sh to get the right
> format. Comments should start with a capital letter, be full
> sentences, and end with a period followed by 2 spaces.
>
> see below.....
>
> diff -rupPN gdb-5.2.1/gdb/config/powerpc/ppc64linux.mh src.ppc64/gdb/config/powerpc/ppc64linux.mh
> --- gdb-5.2.1/gdb/config/powerpc/ppc64linux.mh 1969-12-31 18:00:00.000000000 -0600
> +++ src.ppc64/gdb/config/powerpc/ppc64linux.mh 2003-03-05 13:00:33.000000000 -0600
> @@ -0,0 +1,14 @@
> +# Host: PowerPC, running Linux
> +
> +XM_FILE= xm-linux.h
> +XM_CLIBS=
> +
> +NAT_FILE= nm-linux.h
> +NATDEPFILES= infptrace.o inftarg.o fork-child.o corelow.o linux-proc.o \
> + core-regset.o ppc-linux-nat.o proc-service.o thread-db.o lin-lwp.o \
> + gcore.o ppc-sysv-tdep.o
> +
>
> this is the host makefile fragment, the *tdep.o files should be
> included in the target makefile fragment, the .mt file, not here.
> Actually if you exclude the .o's that ashould really be in the mt
> file, then this file becomes almost identical to the linux.mh
> file. Which makes me wonder if we really need a new file.
>
> +LOADLIBES = -ldl -lthread_db
> +
>
> Why include thread_db? I don't see any other config files doing that.
>
> +GDBSERVER_DEPFILES= low-linux.o
>
> it is linux-low.o
>
> +GDBSERVER_LIBS= -lnss_dns -lnss_files -lresolv
Actually, those lines are obsolete. It's on my list to go through and
remove them all so people don't keep copying them.
> diff -rupPN gdb-5.2.1/gdb/elfread.c src.ppc64/gdb/elfread.c
> --- gdb-5.2.1/gdb/elfread.c 2002-03-25 10:50:20.000000000 -0600
> +++ src.ppc64/gdb/elfread.c 2003-01-28 13:28:24.000000000 -0600
> @@ -154,6 +154,12 @@ record_minimal_symbol_and_info (char *na
> if (ms_type == mst_text || ms_type == mst_file_text)
> address = SMASH_TEXT_ADDRESS (address);
>
> +#ifdef DROP_TEXT_NAME_PREFIX_CHAR
> + if ((ms_type == mst_text || ms_type == mst_file_text)
> + && name[0] == DROP_TEXT_NAME_PREFIX_CHAR)
> + ++name;
> +#endif /* DROP_TEXT_NAME_PREFIX_CHAR */
> +
>
>
> can you explain why this is needed? Do we really have names starting
> with '.', using gcc?
This is a peculiarity of the PPC64 ABI, also related to the OPD macros.
Global functions have two symbols: 'foo' and '.foo'. One of them is
an address and the other is a descriptor with the function's gp value,
IIRC.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-05-07 20:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-17 22:44 Will Schmidt
2003-05-07 20:14 ` Andrew Cagney
2003-05-07 20:37 ` Elena Zannoni
2003-05-07 20:46 ` Daniel Jacobowitz [this message]
2003-05-09 21:05 ` Jim Blandy
2003-05-13 22:33 ` Jim Blandy
2003-05-12 14:34 Will Schmidt
2003-05-13 22:59 Will Schmidt
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=20030507204601.GA25740@nevyn.them.org \
--to=drow@mvista.com \
--cc=ezannoni@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=will_schmidt@vnet.ibm.com \
--cc=willschm@us.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