From: Indu Bhagat <ibhagat@sourceware.org>
To: bfd-cvs@sourceware.org
Subject: [binutils-gdb] gas: sframe: fix some typos in code comments
Date: Sat, 6 Jan 2024 11:16:55 +0000 (GMT) [thread overview]
Message-ID: <20240106111655.656523858D1E@sourceware.org> (raw)
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=a2c02fa6ee6a5b01f516e340f3e3855fee7e0834
commit a2c02fa6ee6a5b01f516e340f3e3855fee7e0834
Author: Indu Bhagat <indu.bhagat@oracle.com>
Date: Sat Jan 6 03:05:44 2024 -0800
gas: sframe: fix some typos in code comments
Diff:
---
gas/gen-sframe.c | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/gas/gen-sframe.c b/gas/gen-sframe.c
index f8a70330582..3c212f3a882 100644
--- a/gas/gen-sframe.c
+++ b/gas/gen-sframe.c
@@ -407,7 +407,7 @@ sframe_get_fre_offset_size (struct sframe_row_entry *sframe_fre)
#if SFRAME_FRE_TYPE_SELECTION_OPT
-/* Create a composite exression CEXP (for SFrame FRE start address) such that:
+/* Create a composite expression CEXP (for SFrame FRE start address) such that:
exp = <val> OP_absent <width>, where,
@@ -449,7 +449,7 @@ create_fre_start_addr_exp (expressionS *cexp, symbolS *fre_pc_begin,
cexp->X_add_number = 0;
}
-/* Create a composite exression CEXP (for SFrame FDE function info) such that:
+/* Create a composite expression CEXP (for SFrame FDE function info) such that:
exp = <rest_of_func_info> OP_modulus <width>, where,
@@ -458,7 +458,7 @@ create_fre_start_addr_exp (expressionS *cexp, symbolS *fre_pc_begin,
used to stash away the func_info. The upper 4-bits of the func_info are copied
back to the resulting byte by the fragment fixup logic.
- <width> stores the expression when evaluated gives the size of the
- funtion in number of bytes.
+ function in number of bytes.
The use of OP_modulus as the X_op_symbol helps identify this expression
later when fragments are fixed up. */
@@ -631,7 +631,7 @@ output_sframe_internal (void)
addr_size = SFRAME_RELOC_SIZE;
- /* The function desciptor entries as dumped by the assembler are not
+ /* The function descriptor entries as dumped by the assembler are not
sorted on PCs. */
unsigned char sframe_flags = 0;
sframe_flags |= !SFRAME_F_FDE_SORTED;
@@ -673,10 +673,10 @@ output_sframe_internal (void)
#endif
out_one (fixed_ra_offset);
- /* None of the AMD64, or AARCH64 ABIs need the auxilliary header.
+ /* None of the AMD64, or AARCH64 ABIs need the auxiliary header.
When the need does arise to use this field, the appropriate backend
must provide this information. */
- out_one (0); /* Auxilliary SFrame header length. */
+ out_one (0); /* Auxiliary SFrame header length. */
out_four (num_fdes); /* Number of FDEs. */
out_four (num_fres); /* Number of FREs. */
@@ -1085,7 +1085,7 @@ sframe_xlate_do_val_offset (struct sframe_xlate_ctx *xlate_ctx ATTRIBUTE_UNUSED,
{
/* Previous value of register is CFA + offset. However, if the specified
register is not interesting (FP or RA reg), the current DW_CFA_val_offset
- instruction can be safely skipped without sacrificing the asynchonicity of
+ instruction can be safely skipped without sacrificing the asynchronicity of
stack trace information. */
if (cfi_insn->u.r == SFRAME_CFA_FP_REG)
return SFRAME_XLATE_ERR_NOTREPRESENTED; /* Not represented. */
reply other threads:[~2024-01-06 11:16 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=20240106111655.656523858D1E@sourceware.org \
--to=ibhagat@sourceware.org \
--cc=bfd-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: 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).