All of lore.kernel.org
 help / color / mirror / Atom feed
From: jamie@shareable.org (Jamie Lokier)
To: linux-arm-kernel@lists.infradead.org
Subject: 32-bit Thumb-2 breakpoints
Date: Mon, 11 Jan 2010 23:10:27 +0000	[thread overview]
Message-ID: <20100111231027.GA30714@shareable.org> (raw)
In-Reply-To: <20100111225436.GA7408@caradoc.them.org>

Daniel Jacobowitz wrote:
> In the example from my mail:
> 
>    cmp   r0, r0
>    itt   eq
> A: cmpeq r0, r1
> B: moveq r0, r2
> C: nop
> 
> The cmpeq can be an adcs.w, eors.w, et cetera.  We're at A, trying to
> figure out whether to put a breakpoint on B or C (both of which could
> validly be branches).
>
> It's possible I've missed something obvious, of course!

I couldn't really tell from a quick glance at the net, which only
half-explained itt, so I'll ask some newbie-sounding questions just in
case it is something obvious.

Isn't the itt sequence for Thumb-2 supposed to be consistent with the
condition sequence for ARM, so that it should be:

    cmp   r0, r0
    itt   eq
 A: cmpeq r0, r1
 B: movne r0, r2   <- that is, ne not eq, because it's the "then" branch
 C: nop

And does the cmp at A really affect execution of the instructions at B
and C in a Thumb-2 itt sequence, rather than the condition being
checked once@the time of the itt instruction and played out for the
following 3 instructions?

Thanks,
-- Jamie

  reply	other threads:[~2010-01-11 23:10 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-11 21:58 32-bit Thumb-2 breakpoints Daniel Jacobowitz
2010-01-11 22:35 ` Russell King - ARM Linux
2010-01-11 22:54   ` Daniel Jacobowitz
2010-01-11 23:10     ` Jamie Lokier [this message]
2010-01-11 23:15       ` Russell King - ARM Linux
2010-01-12  0:15         ` Jamie Lokier
2010-01-11 23:17       ` Daniel Jacobowitz
2010-01-12  0:17         ` Jamie Lokier
2010-01-12  0:22           ` Daniel Jacobowitz
2010-02-03 17:23         ` Jamie Lokier
2010-02-03 17:44           ` Daniel Jacobowitz
2010-02-04 22:46             ` Pavel Machek
2010-01-11 23:31     ` Russell King - ARM Linux
2010-01-11 23:51       ` Daniel Jacobowitz
2010-01-12  9:53         ` Catalin Marinas
2010-01-12 10:34 ` Catalin Marinas
2010-01-12 14:25   ` Daniel Jacobowitz
2010-01-28 20:21     ` Daniel Jacobowitz
2010-02-02 22:43       ` Russell King - ARM Linux
2010-02-03  0:50         ` Daniel Jacobowitz
2010-02-03 11:52           ` Catalin Marinas
2010-02-03 13:28             ` Russell King - ARM Linux
2010-02-03 13:48               ` Daniel Jacobowitz
2010-02-03 14:43                 ` Russell King - ARM Linux
2010-02-03 14:56                   ` Daniel Jacobowitz
2010-02-03 13:59               ` Jamie Iles
2010-02-03 14:40                 ` Russell King - ARM Linux
2010-02-03 15:31                   ` Jamie Iles
2010-02-03 16:01                     ` Will Deacon
2010-02-03 15:02               ` Matthieu CASTET
2010-02-03 15:04                 ` Catalin Marinas
2010-02-03 15:19                   ` Nicolas Pitre
2010-02-03 15:19                 ` Daniel Jacobowitz
2010-02-03 15:30                   ` Russell King - ARM Linux
2010-02-03 15:35                     ` Daniel Jacobowitz
2010-02-03 16:35                       ` Russell King - ARM Linux
2010-02-03 17:45                         ` Daniel Jacobowitz
2010-02-03 15:35                   ` Nicolas Pitre

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=20100111231027.GA30714@shareable.org \
    --to=jamie@shareable.org \
    --cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.