public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vapier at gentoo dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug sim/18407] Bfin simulator - error in handling >>> (S), when shift value > 16
Date: Wed, 13 May 2015 16:56:00 -0000	[thread overview]
Message-ID: <bug-18407-4717-HgzEHF1Kro@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18407-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=18407

--- Comment #4 from Mike Frysinger <vapier at gentoo dot org> ---
i'm not terribly interested in how the vdsp sim operates :).  the gnu sim
should match the hardware.  if you're seeing a diff between bf532 in the sim
and real hardware, then that def needs fixing.

unfortunately i'm traveling atm and won't have access to bfin hardware for a
while to run some tests.

wrt objdump, i agree it's a bit weird.  i'll take a look at that too.  there
are some cases where the hardware actually respects the full shift amount even
though it's not documented in the PRM.  the disassembler can also be pretty
basic in its decoding ... i've been meaning to sync the sim & opcodes at some
point.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2015-05-13 16:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-13 11:02 [Bug sim/18407] New: " igorr at gitatechnologies dot com
2015-05-13 11:06 ` [Bug sim/18407] " igorr at gitatechnologies dot com
2015-05-13 11:12 ` igorr at gitatechnologies dot com
2015-05-13 16:02 ` vapier at gentoo dot org
2015-05-13 16:16 ` igorr at gitatechnologies dot com
2015-05-13 16:56 ` vapier at gentoo dot org [this message]
2015-10-11  7:43 ` cvs-commit at gcc dot gnu.org

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=bug-18407-4717-HgzEHF1Kro@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).