Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <kettenis@chello.nl>
To: gdb-patches@sources.redhat.com
Subject: [PATCH] Fix amd64 compilation
Date: Sat, 31 May 2003 16:54:00 -0000	[thread overview]
Message-ID: <200305311654.h4VGsbuG007807@elgar.kettenis.dyndns.org> (raw)

Apparently Andrew missed the push_dummy_call() in x86-64-tdep.c.

Committed.

Index: ChangeLog
from  Mark Kettenis  <kettenis@gnu.org>
 
	* x86-64-tdep.c (x86_64_push_dummy_call): Adjust for changed
	function signature.

Index: x86-64-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/x86-64-tdep.c,v
retrieving revision 1.74
diff -u -p -r1.74 x86-64-tdep.c
--- x86-64-tdep.c 31 May 2003 16:49:18 -0000 1.74
+++ x86-64-tdep.c 31 May 2003 16:52:25 -0000
@@ -754,9 +754,10 @@ x86_64_store_return_value (struct type *
 \f
 
 static CORE_ADDR
-x86_64_push_dummy_call (struct gdbarch *gdbarch, struct regcache *regcache,
-			CORE_ADDR dummy_addr, int nargs, struct value **args,
-			CORE_ADDR sp, int struct_return, CORE_ADDR struct_addr)
+x86_64_push_dummy_call (struct gdbarch *gdbarch, CORE_ADDR func_addr,
+			struct regcache *regcache, CORE_ADDR bp_addr,
+			int nargs, struct value **args,	CORE_ADDR sp,
+			int struct_return, CORE_ADDR struct_addr)
 {
   char buf[8];
 
@@ -772,7 +773,7 @@ x86_64_push_dummy_call (struct gdbarch *
 
   /* Store return address.  */
   sp -= 8;
-  store_unsigned_integer (buf, 8, dummy_addr);
+  store_unsigned_integer (buf, 8, bp_addr);
   write_memory (sp, buf, 8);
 
   /* Finally, update the stack pointer...  */


             reply	other threads:[~2003-05-31 16:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-31 16:54 Mark Kettenis [this message]
2003-05-31 17:20 ` Andrew Cagney
2003-06-01  9:48   ` Mark Kettenis

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=200305311654.h4VGsbuG007807@elgar.kettenis.dyndns.org \
    --to=kettenis@chello.nl \
    --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