public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Tom Tromey <tromey@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] Cosmetic fix in ppc-sysv-tdep.c Date: Tue, 6 Dec 2022 16:01:02 +0000 (GMT) [thread overview] Message-ID: <20221206160102.9D4DD383FD74@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=53fd08b60d8183af2a6a6820677bfd01716bc992 commit 53fd08b60d8183af2a6a6820677bfd01716bc992 Author: Tom Tromey <tromey@adacore.com> Date: Tue Dec 6 08:59:09 2022 -0700 Cosmetic fix in ppc-sysv-tdep.c This is just a couple of cosmetic fixes in ppc-sysv-tdep.c: fixing some formatting and correcting a typo. Diff: --- gdb/ppc-sysv-tdep.c | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/gdb/ppc-sysv-tdep.c b/gdb/ppc-sysv-tdep.c index 1cbaaf2a4e6..32d00723566 100644 --- a/gdb/ppc-sysv-tdep.c +++ b/gdb/ppc-sysv-tdep.c @@ -2157,13 +2157,14 @@ ppc64_sysv_abi_return_value (struct gdbarch *gdbarch, struct value *function, return RETURN_VALUE_STRUCT_CONVENTION; } -CORE_ADDR ppc64_sysv_get_return_buf_addr (struct type *val_type, - frame_info_ptr cur_frame) +CORE_ADDR +ppc64_sysv_get_return_buf_addr (struct type *val_type, + frame_info_ptr cur_frame) { /* The PowerPC ABI specifies aggregates that are not returned by value are returned in a storage buffer provided by the caller. The address of the storage buffer is provided as a hidden first input - arguement in register r3. The PowerPC ABI does not guarantee that + argument in register r3. The PowerPC ABI does not guarantee that register r3 will not be changed while executing the function. Hence, it cannot be assumed that r3 will still contain the address of the storage buffer when execution reaches the end of the function.
reply other threads:[~2022-12-06 16:01 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=20221206160102.9D4DD383FD74@sourceware.org \ --to=tromey@sourceware.org \ --cc=gdb-cvs@sourceware.org \ /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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).