From: Nathan Froyd <froydnj@codesourcery.com>
To: gdb-patches@sourceware.org
Subject: [PATCH,sim] properly handle sync instruction variants
Date: Mon, 12 Jan 2009 18:10:00 -0000 [thread overview]
Message-ID: <20090112180954.GV28711@codesourcery.com> (raw)
Recent Power ISAs have included the ability to control the type of
memory accesses ordered by the `sync' instruction by means of a two-bit
field. The patch below modifies the ppc simulator's instruction
description to take note of this two-bit field.
Tested on powerpc-none-eabi, where it fixes ~140 g++ testsuite failures
and a handful of gcc failures. OK to commit?
-Nathan
cvs diff: Diffing .
Index: ChangeLog
===================================================================
RCS file: /cvs/src/src/sim/ppc/ChangeLog,v
retrieving revision 1.87
diff -u -u -r1.87 ChangeLog
--- ChangeLog 15 Dec 2008 19:48:06 -0000 1.87
+++ ChangeLog 12 Jan 2009 18:04:27 -0000
@@ -1,3 +1,7 @@
+2009-01-12 Nathan Froyd <froydnj@codesourcery.com>
+
+ * ppc-instructions (sync): Add L field.
+
2008-12-15 Joel Sherrill <joel.sherrill@oarcorp.com>
* ppc-instructions, ppc-spr-table: Add ability
Index: ppc-instructions
===================================================================
RCS file: /cvs/src/src/sim/ppc/ppc-instructions,v
retrieving revision 1.10
diff -u -u -r1.10 ppc-instructions
--- ppc-instructions 15 Dec 2008 19:48:06 -0000 1.10
+++ ppc-instructions 12 Jan 2009 18:04:27 -0000
@@ -2494,7 +2494,7 @@
}
PPC_INSN_INT(0, (RA_BITMASK & ~1) | RB_BITMASK | RS_BITMASK, 1/*Rc*/);
-0.31,6./,11./,16./,21.598,31./:X::sync:Synchronize
+0.31,6./,9.L,11./,16./,21.598,31./:X::sync:Synchronize
*601: PPC_UNIT_IU, PPC_UNIT_IU, 1, 1, 0
*603: PPC_UNIT_SRU, PPC_UNIT_SRU, 1, 1, 0
*603e:PPC_UNIT_SRU, PPC_UNIT_SRU, 1, 1, 0
next reply other threads:[~2009-01-12 18:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 18:10 Nathan Froyd [this message]
2009-01-12 19:11 ` Daniel Jacobowitz
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=20090112180954.GV28711@codesourcery.com \
--to=froydnj@codesourcery.com \
--cc=gdb-patches@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