From: Andrew Cagney <ac131313@cygnus.com>
To: "Pierre Saucourt-Harmel (r54698)" <pierre.saucourt-harmel@motorola.com>
Cc: gdb@sourceware.cygnus.com, crossgcc@sources.redhat.com
Subject: Re: Execution pipeline (2nd)
Date: Sat, 17 Feb 2001 10:51:00 -0000 [thread overview]
Message-ID: <3A8E4425.33AA366D@cygnus.com> (raw)
In-Reply-To: <3A8CF11F.2E4EE510@motorola.com>
"Pierre Saucourt-Harmel (r54698)" wrote:
>
> Hi.
>
> Any idea if yes or no, GDB v5.0 is able to take into account the
> execution pipeline of a processor, such as the ARM7T, when this
> pipeline has consequences on the external programing model of the
> processor ?
No. GDB assumes that the target it is looking at has synchronised (a
PPC term) its self draining all pipelines.
Andrew
prev parent reply other threads:[~2001-02-17 10:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-13 9:04 Execution pipeline Pierre Saucourt-Harmel (r54698)
2001-02-16 1:16 ` Execution pipeline (2nd) Pierre Saucourt-Harmel (r54698)
2001-02-17 10:51 ` Andrew Cagney [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=3A8E4425.33AA366D@cygnus.com \
--to=ac131313@cygnus.com \
--cc=crossgcc@sources.redhat.com \
--cc=gdb@sourceware.cygnus.com \
--cc=pierre.saucourt-harmel@motorola.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).