Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Burgess <andrew.burgess@embecosm.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org, Jim Wilson <jimw@sifive.com>,
	Palmer Dabbelt <palmer@sifive.com>
Subject: Re: [PATCH] gdb/riscv: Don't error when decoding a 6 or 8 byte instruction
Date: Wed, 05 Jun 2019 09:38:00 -0000	[thread overview]
Message-ID: <20190605093820.GE23204@embecosm.com> (raw)
In-Reply-To: <998212a3-4a1d-12ad-2a16-aa05a0e4101c@redhat.com>

* Pedro Alves <palves@redhat.com> [2019-06-05 10:12:12 +0100]:

> On 6/4/19 12:50 PM, Andrew Burgess wrote:
> > +	   prologue scanner will try to decode it.  These long
> > +	   instructions are ISA extensions, I use .byte rather than an
> > +	   actual instruction mnemonic so that the test can be compiled
> 
> Tiny nit, but please avoid "I" in comments.  Either just don't use a
> pronoun, e.g.:
> 
>    Since these long instructions are ISA extensions, use .byte
> 
> or use "we" instead.

I pushed the patch below.

Thanks,
Andrew

--

commit 0088ba596bba2e0b94139f1c2c4f5875848edbd6
Author: Andrew Burgess <andrew.burgess@embecosm.com>
Date:   Wed Jun 5 10:33:54 2019 +0100

    gdb/testsuite: Improve comments in recently added test
    
    Remove the use of 'I' within some comments in a recently added test.
    
    gdb/testsuite/ChangeLog:
    
            * gdb.arch/riscv-unwind-long-insn-6.s: Remove use of 'I' in
            comment.
            * gdb.arch/riscv-unwind-long-insn-8.s: Likewise.

diff --git a/gdb/testsuite/gdb.arch/riscv-unwind-long-insn-6.s b/gdb/testsuite/gdb.arch/riscv-unwind-long-insn-6.s
index b21b1e10f32..9bbc0ca429b 100644
--- a/gdb/testsuite/gdb.arch/riscv-unwind-long-insn-6.s
+++ b/gdb/testsuite/gdb.arch/riscv-unwind-long-insn-6.s
@@ -29,7 +29,7 @@ bar:
 func:
         /* A fake 6 byte instruction.  This is never executed, but the
 	   prologue scanner will try to decode it.  These long
-	   instructions are ISA extensions, I use .byte rather than an
+	   instructions are ISA extensions, use .byte rather than an
 	   actual instruction mnemonic so that the test can be compiled
 	   with a toolchain that doesn't include any long instruction
 	   extensions.  */
diff --git a/gdb/testsuite/gdb.arch/riscv-unwind-long-insn-8.s b/gdb/testsuite/gdb.arch/riscv-unwind-long-insn-8.s
index 3fad07b59dd..0bf86940a7b 100644
--- a/gdb/testsuite/gdb.arch/riscv-unwind-long-insn-8.s
+++ b/gdb/testsuite/gdb.arch/riscv-unwind-long-insn-8.s
@@ -29,7 +29,7 @@ bar:
 func:
         /* A fake 8 byte instruction.  This is never executed, but the
 	   prologue scanner will try to decode it.  These long
-	   instructions are ISA extensions, I use .byte rather than an
+	   instructions are ISA extensions, use .byte rather than an
 	   actual instruction mnemonic so that the test can be compiled
 	   with a toolchain that doesn't include any long instruction
 	   extensions.  */


      reply	other threads:[~2019-06-05  9:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-04 11:51 Andrew Burgess
2019-06-04 16:36 ` John Baldwin
2019-06-04 23:49 ` Palmer Dabbelt
2019-06-05  9:08 ` Andrew Burgess
2019-06-05  9:12 ` Pedro Alves
2019-06-05  9:38   ` Andrew Burgess [this message]

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=20190605093820.GE23204@embecosm.com \
    --to=andrew.burgess@embecosm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jimw@sifive.com \
    --cc=palmer@sifive.com \
    --cc=palves@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