From: Manoj Iyer <manjo@austin.ibm.com>
To: gdb-patches@sources.redhat.com
Subject: [PATCH] GDB64 ppc64 compile error patch
Date: Wed, 07 Apr 2004 19:45:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.58.0404071418140.9321@lazy> (raw)
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1614 bytes --]
This patch fixes compile error when gdb is built as a 64bit binary on a
PPC64 platform. ELF_NGREG ELF_NFPREG and ELF_NVRREG are members of an
enum, but they are also defined in a headerfile, so compiler issues error.
gcc -c -m64 -mminimal-toc -I. -I. -I./config
-DLOCALEDIR="\"/usr/local/share/locale\"" -DHAVE_CONFIG_H
-I./../include/opcode -I./../readline/.. -I../bfd -I./../bfd
-I./../include -I../intl -I./../intl -DMI_OUT=1 -Wimplicit -Wreturn-type
-Wcomment -Wtrigraphs -Wformat -Wparentheses -Wpointer-arith
-Wuninitialized -Wformat-nonliteral -Wunused-label -Wunused-function
ppc-linux-tdep.c
cc1: warning: -Wuninitialized is not supported without -O
ppc-linux-tdep.c:956: error: parse error before numeric constant
make[1]: *** [ppc-linux-tdep.o] Error 1
make[1]: Leaving directory `/root/manjo/April07/xxx/new/src/gdb'
make: *** [all-gdb] Error 2
This is because ELF_NGREG ELF_NFPREG and ELF_NVRREG are defined in header
files
/usr/include/sys/procfs.h:#define ELF_NFPREG 33 /* includes
fpscr */
/usr/include/sys/procfs.h:typedef elf_fpreg_t elf_fpregset_t[ELF_NFPREG];
/usr/include/asm-ppc/elf.h:#define ELF_NFPREG 33 /* includes fpscr
*/
/usr/include/asm-ppc/elf.h:typedef elf_fpreg_t elf_fpregset_t[ELF_NFPREG];
/usr/include/asm-ppc64/elf.h:#define ELF_NFPREG 33 /* includes fpscr
*/
/usr/include/asm-ppc64/elf.h:typedef elf_fpreg_t
elf_fpregset_t[ELF_NFPREG];
and the enum
enum {
ELF_NGREG = 48,
ELF_NFPREG = 33,
ELF_NVRREG = 33
};
causes the compiler to interpret ELF_NFPREG = 33, as 33 = 33, etc.
The patch attached fixes this error.
Thanks
Manoj Iyer
[-- Attachment #2: GDB64 PPC64 patch --]
[-- Type: TEXT/PLAIN, Size: 792 bytes --]
diff -Naurd old/src/gdb/ppc-linux-tdep.c new/src/gdb/ppc-linux-tdep.c
--- old/src/gdb/ppc-linux-tdep.c 2004-02-16 16:49:22.000000000 -0500
+++ new/src/gdb/ppc-linux-tdep.c 2004-04-07 14:24:48.158014232 -0500
@@ -36,6 +36,10 @@
#include "solib-svr4.h"
#include "ppc-tdep.h"
+#define ELF_NGREG 48
+#define ELF_NFPREG 33
+#define ELF_NVRREG 33
+
/* The following instructions are used in the signal trampoline code
on GNU/Linux PPC. The kernel used to use magic syscalls 0x6666 and
0x7777 but now uses the sigreturn syscalls. We check for both. */
@@ -951,13 +955,6 @@
return addr;
}
-
-enum {
- ELF_NGREG = 48,
- ELF_NFPREG = 33,
- ELF_NVRREG = 33
-};
-
enum {
ELF_GREGSET_SIZE = (ELF_NGREG * 4),
ELF_FPREGSET_SIZE = (ELF_NFPREG * 8)
next reply other threads:[~2004-04-07 19:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-07 19:45 Manoj Iyer [this message]
2004-04-07 21:10 ` Kevin Buettner
2004-04-07 21:13 ` Daniel Jacobowitz
[not found] ` <Pine.LNX.4.58.0404071631450.19885@lazy>
2004-04-08 17:02 ` [RFC] " Kevin Buettner
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=Pine.LNX.4.58.0404071418140.9321@lazy \
--to=manjo@austin.ibm.com \
--cc=gdb-patches@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