From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: [PATCH] Eliminate ELF_OBJECT_FORMAT macro
Date: Mon, 08 Apr 2002 18:11:00 -0000 [thread overview]
Message-ID: <1020409011034.ZM22613@localhost.localdomain> (raw)
The patch below eliminates ELF_OBJECT_FORMAT. This macro used to be
used to conditionally enable or disable code in rs6000-tdep.c related
to SysV or EABI issues. Actually, it still does disable some code in
rs6000_push_arguments(), ostensibly for EABI support, but
rs6000_push_arguments is no longer used for EABI support.
* config/powerpc/tm-ppc-eabi.h (ELF_OBJECT_FORMAT): Delete.
* rs6000-tdep.c (rs6000_push_arguments): Eliminate
ELF_OBJECT_FORMAT ifdef.
Index: rs6000-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/rs6000-tdep.c,v
retrieving revision 1.46
diff -u -p -r1.46 rs6000-tdep.c
--- rs6000-tdep.c 9 Apr 2002 00:10:09 -0000 1.46
+++ rs6000-tdep.c 9 Apr 2002 00:50:41 -0000
@@ -1039,7 +1039,7 @@ rs6000_push_arguments (int nargs, struct
ran_out_of_registers_for_arguments:
saved_sp = read_sp ();
-#ifndef ELF_OBJECT_FORMAT
+
/* location for 8 parameters are always reserved. */
sp -= wordsize * 8;
@@ -1048,7 +1048,6 @@ ran_out_of_registers_for_arguments:
/* stack pointer must be quadword aligned */
sp &= -16;
-#endif
/* if there are more arguments, allocate space for them in
the stack, then push them starting from the ninth one. */
Index: config/powerpc/tm-ppc-eabi.h
===================================================================
RCS file: /cvs/src/src/gdb/config/powerpc/tm-ppc-eabi.h,v
retrieving revision 1.8
diff -u -p -r1.8 tm-ppc-eabi.h
--- config/powerpc/tm-ppc-eabi.h 20 Jan 2002 19:26:49 -0000 1.8
+++ config/powerpc/tm-ppc-eabi.h 9 Apr 2002 00:50:42 -0000
@@ -36,9 +36,6 @@
#undef TEXT_SEGMENT_BASE
#define TEXT_SEGMENT_BASE 1
-/* Say that we're using ELF, not XCOFF. */
-#define ELF_OBJECT_FORMAT 1
-
/* The value of symbols of type N_SO and N_FUN maybe null when
it shouldn't be. */
#define SOFUN_ADDRESS_MAYBE_MISSING
reply other threads:[~2002-04-09 1:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1020409011034.ZM22613@localhost.localdomain \
--to=kevinb@redhat.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