Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kyle McMartin <kmcmarti@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCHv3] aarch64: detect atomic sequences like other ll/sc architectures
Date: Thu, 24 Apr 2014 16:06:00 -0000	[thread overview]
Message-ID: <20140424160604.GD7588@redacted.bos.redhat.com> (raw)
In-Reply-To: <20140424125557.GG18355@adacore.com>

On Thu, Apr 24, 2014 at 05:55:57AM -0700, Joel Brobecker wrote:
> > 2014-04-22  Kyle McMartin  <kyle@redhat.com>
> > 
> > gdb:
> >         * aarch64-tdep.c (aarch64_deal_with_atomic_sequence): New function.
> >         (aarch64_gdbarch_init): Handle single stepping of atomic sequences
> >         with aarch64_deal_with_atomic_sequence.
> > 
> > gdb/testsuite:
> >         * gdb.arch/aarch64-atomic-inst.c: New file.
> >         * gdb.arch/aarch64-atomic-inst.exp: New file.
> 
> This looks good to me. You just forgot to change the name of
> the new function in the ChangeLog entry.  Also, a couple of
> really minor nits that I happen to spot in your patch below,
> but they only affect formatting, so the patch is pre-approved.
> 

Thanks! I'll fix the nits below & the changelog and send a v4. Would you
be willing to commit?

> > +      /* Check if the instruction is a conditional branch.  */
> > +      if (decode_bcond (loc, insn, &cond, &offset))
> > +	{
> > +
> > +	  if (bc_insn_count >= 1)
> > +	    return 0;
> 
> Did you mean to leave an empty line at the start of the if block?
> Not a problem if yoi meant to, but a little unusual, so I thought
> I'd ask.
> 

No, my mistake, I had some local variables here that I removed.

> 
> > +
> > +	  /* It is, so we'll try to set a breakpoint at the destination.  */
> > +	  breaks[1] = loc + offset;
> > +
> > +	  bc_insn_count++;
> > +	  last_breakpoint++;
> > +	}
> > +
> > +      /* Look for the Store Exclusive which closes the atomic sequence.  */
> > +      if (decode_masked_match (insn, 0x3fc00000, 0x08000000))
> > +	{
> > +          closing_insn = loc;
> > +	  break;
> 
> Indentation should be tabs first, and then spaces. I know it's a PITA,
> but unfortunately something we try to follow in the GDB project. Can
> you fix the "closing_insn" line?
> 

Absolutely, my bad.

> Thanks,
> -- 
> Joel

regards, Kyle


  reply	other threads:[~2014-04-24 16:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-22 16:55 Kyle McMartin
2014-04-24 12:56 ` Joel Brobecker
2014-04-24 16:06   ` Kyle McMartin [this message]
2014-04-24 16:16     ` Joel Brobecker

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=20140424160604.GD7588@redacted.bos.redhat.com \
    --to=kmcmarti@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@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