public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "wilson at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug sim/27483] aarch64: adds test failing when adding 0x80000000 & 0xffffffff
Date: Thu, 08 Apr 2021 01:59:26 +0000 [thread overview]
Message-ID: <bug-27483-4717-ysjqtb70ah@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27483-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27483
Jim Wilson <wilson at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|NEW |RESOLVED
Assignee|nickc at redhat dot com |wilson at gcc dot gnu.org
--- Comment #9 from Jim Wilson <wilson at gcc dot gnu.org> ---
I tried fixing set_flags_for_add32 to look like set_flags_for_add64, and the
simulator ends up about 1.5% slower using dhrystone as the testcase. This is
cleaner, but seems a bit too much of a slow down, and probably explains why the
function is written this way. With the fix I checked in, the simulator is
about 0.7% slower which is within my measurement error so a more acceptable
slow down.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2021-04-08 1:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-28 6:35 [Bug sim/27483] New: " vapier at gentoo dot org
2021-03-01 4:48 ` [Bug sim/27483] " wilson at gcc dot gnu.org
2021-03-01 8:30 ` schwab@linux-m68k.org
2021-03-01 16:43 ` wilson at gcc dot gnu.org
2021-03-01 16:55 ` schwab@linux-m68k.org
2021-03-01 23:28 ` wilson at gcc dot gnu.org
2021-03-02 8:43 ` schwab@linux-m68k.org
2021-03-07 18:48 ` vapier at gentoo dot org
2021-04-08 1:53 ` cvs-commit at gcc dot gnu.org
2021-04-08 1:59 ` wilson at gcc dot gnu.org [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-27483-4717-ysjqtb70ah@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).