Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Recognize branch instruction on MIPS in gdb.trace/entry-values.exp
Date: Thu, 08 Jan 2015 01:10:00 -0000	[thread overview]
Message-ID: <87oaqat6uj.fsf@codesourcery.com> (raw)
In-Reply-To: <alpine.LFD.2.11.1501072207140.27020@eddie.linux-mips.org>	(Maciej W. Rozycki's message of "Wed, 7 Jan 2015 23:22:22 +0000")

"Maciej W. Rozycki" <macro@linux-mips.org> writes:

>  Overall I'd prefer MIPS instructions to be spelled out capitalised in our 
> documentation for consistency with hardware documentation.  This makes 
> them more prominent in text and also avoids confusing them with common 
> words such as in `AND' vs `and'.  The only exception are quoted pieces of 
> assembly code where the language specifies mnemonics as lowercase strings.
>

OK, that is fine to me.

>>  If it is jalrc, set
>> +    # RETURNED_FROM_FOO to insn1, otherwise set RETURNED_FROM_FOO to
>> +    # insn2.
>> +    set call_insn {jalrc|[jb]al[sxr]*[ \t][^\r\n]+\r\n}
>
>  OK, this should work.  I have a minor nit yet: `[sxr]?' will be more 
> accurate than `[sxr]*', you want to see the letter at most once.  The 
> former regexp will likely interpret faster too.

We want to match JALRS, so [sxr]* is needed here.

-- 
Yao (齐尧)


  reply	other threads:[~2015-01-08  1:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-29  8:15 Yao Qi
2014-12-29 23:20 ` Maciej W. Rozycki
2014-12-30 12:34   ` Yao Qi
2014-12-30 14:17     ` Maciej W. Rozycki
2015-01-04  8:42       ` Yao Qi
2015-01-07 23:22         ` Maciej W. Rozycki
2015-01-08  1:10           ` Yao Qi [this message]
2015-01-08  1:24             ` Maciej W. Rozycki
2015-01-08  3:47               ` Yao Qi

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=87oaqat6uj.fsf@codesourcery.com \
    --to=yao@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=macro@linux-mips.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