public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "nickc at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug sim/8387] sim: arm: Thumb add pc,rn should not word align pc
Date: Wed, 02 Nov 2022 16:46:59 +0000	[thread overview]
Message-ID: <bug-8387-4717-azJOcNGbz7@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-8387-4717@http.sourceware.org/bugzilla/>

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

Nick Clifton <nickc at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |NEW

--- Comment #4 from Nick Clifton <nickc at redhat dot com> ---
(In reply to Luis Machado from comment #3)
> Hi Nick, are you still planning to address this?

No.  I looked at the proposed patch, and I can see how it would fix the problem
in the testcase shown.  But I feel that it is likely to break other code
sequences because of its change to the LHS definition.  Unfortunately my
knowledge of the ARM ISA is now so out of date, that I am not sure that I can
reasonably review the patch.

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

      parent reply	other threads:[~2022-11-02 16:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-8387-4717@http.sourceware.org/bugzilla/>
2014-03-14  0:46 ` [Bug sim/8387] " vapier at gentoo dot org
2015-03-29 22:07 ` vapier at gentoo dot org
2015-03-29 22:08 ` vapier at gentoo dot org
2021-10-31 17:14 ` [Bug sim/8387] sim: arm: " vapier at gentoo dot org
2022-11-02 11:33 ` luis.machado at arm dot com
2022-11-02 16:46 ` nickc at redhat dot com [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=bug-8387-4717-azJOcNGbz7@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).