From 1a38736e6c8ef0dce69214811f3c2a43c409d69b Mon Sep 17 00:00:00 2001 From: Jim Blandy Date: Tue, 17 Jun 2003 16:06:18 +0000 Subject: [PATCH] * ppc-linux-tdep.c: "Linux" -> "GNU/Linux" --- gdb/ChangeLog | 4 ++++ gdb/ppc-linux-tdep.c | 6 +++--- 2 files changed, 7 insertions(+), 3 deletions(-) diff --git a/gdb/ChangeLog b/gdb/ChangeLog index 462b20d07e5..47e663fd3a3 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,3 +1,7 @@ +2003-06-17 Jim Blandy + + * ppc-linux-tdep.c: "Linux" -> "GNU/Linux" + 2003-06-16 Theodore A. Roth * avr-tdep.c (avr_extract_return_value): New function. diff --git a/gdb/ppc-linux-tdep.c b/gdb/ppc-linux-tdep.c index f2d76b8b11b..ab038b7a2e9 100644 --- a/gdb/ppc-linux-tdep.c +++ b/gdb/ppc-linux-tdep.c @@ -770,12 +770,12 @@ static struct insn_pattern ppc64_standard_linkage[] = (sizeof (ppc64_standard_linkage) / sizeof (ppc64_standard_linkage[0])) -/* Recognize a 64-bit PowerPC Linux linkage function --- what GDB +/* Recognize a 64-bit PowerPC GNU/Linux linkage function --- what GDB calls a "solib trampoline". */ static int ppc64_in_solib_call_trampoline (CORE_ADDR pc, char *name) { - /* Detecting solib call trampolines on PPC64 Linux is a pain. + /* Detecting solib call trampolines on PPC64 GNU/Linux is a pain. It's not specifically solib call trampolines that are the issue. Any call from one function to another function that uses a @@ -787,7 +787,7 @@ ppc64_in_solib_call_trampoline (CORE_ADDR pc, char *name) also an inter-TOC call, and requires a trampoline --- so "solib call trampolines" are just a special case. - The 64-bit PowerPC Linux ABI calls these call trampolines + The 64-bit PowerPC GNU/Linux ABI calls these call trampolines "linkage functions". Since they need to be near the functions that call them, they all appear in .text, not in any special section. The .plt section just contains an array of function -- 2.30.2