mirror of
https://github.com/bminor/binutils-gdb.git
synced 2025-11-16 12:34:43 +00:00
Run gdb/contrib/spellcheck.sh on directory sim. Fix auto-corrected typos: ... accessable -> accessible accidently -> accidentally accomodate -> accommodate adress -> address afair -> affair agains -> against agressively -> aggressively annuled -> annulled arbitary -> arbitrary arround -> around auxillary -> auxiliary availablity -> availability clasic -> classic comming -> coming controled -> controlled controling -> controlling destory -> destroy existance -> existence explictly -> explicitly faciliate -> facilitate fouth -> fourth fullfilled -> fulfilled guarentee -> guarantee hinderance -> hindrance independant -> independent inital -> initial loosing -> losing occurance -> occurrence occured -> occurred occuring -> occurring omited -> omitted oportunity -> opportunity parallely -> parallelly permissable -> permissible postive -> positive powerfull -> powerful preceed -> precede preceeding -> preceding preceeds -> precedes primative -> primitive probaly -> probably programable -> programmable propogate -> propagate propper -> proper recieve -> receive reconized -> recognized refered -> referred refering -> referring relevent -> relevant responisble -> responsible retreive -> retrieve safty -> safety specifiying -> specifying spontanous -> spontaneous sqaure -> square successfull -> successful supress -> suppress sytem -> system thru -> through transfered -> transferred trigered -> triggered unfortunatly -> unfortunately upto -> up to usefull -> useful wierd -> weird writen -> written doesnt -> doesn't isnt -> isn't ... Manually undid the "andd -> and" transformation in sim/testsuite/cr16/andd.cgs and sim/cr16/simops.c. Tested by rebuilding on x86_64-linux. Approved-By: Tom Tromey <tom@tromey.com>
81 lines
2.5 KiB
C
81 lines
2.5 KiB
C
/* This file is part of the program psim.
|
|
|
|
Copyright (C) 1994-1995, Andrew Cagney <cagney@highland.com.au>
|
|
|
|
This program is free software; you can redistribute it and/or modify
|
|
it under the terms of the GNU General Public License as published by
|
|
the Free Software Foundation; either version 3 of the License, or
|
|
(at your option) any later version.
|
|
|
|
This program is distributed in the hope that it will be useful,
|
|
but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
GNU General Public License for more details.
|
|
|
|
You should have received a copy of the GNU General Public License
|
|
along with this program; if not, see <http://www.gnu.org/licenses/>.
|
|
|
|
*/
|
|
|
|
|
|
/* Creates the files semantics.[hc].
|
|
|
|
The generated file semantics contains functions that implement the
|
|
operations required to model a single target processor instruction.
|
|
|
|
Several different variations on the semantics file can be created:
|
|
|
|
o uncached
|
|
|
|
No instruction cache exists. The semantic function
|
|
needs to generate any required values locally.
|
|
|
|
o cached - separate cracker and semantic
|
|
|
|
Two independent functions are created. Firstly the
|
|
function that cracks an instruction entering it into a
|
|
cache and secondly the semantic function proper that
|
|
uses the cache.
|
|
|
|
o cached - semantic + cracking semantic
|
|
|
|
The function that cracks the instruction and enters
|
|
all values into the cache also contains a copy of the
|
|
semantic code (avoiding the need to call both the
|
|
cracker and the semantic function when there is a
|
|
cache miss).
|
|
|
|
For each of these general forms, several refinements can occure:
|
|
|
|
o do/don't duplicate/expand semantic functions
|
|
|
|
As a consequence of decoding an instruction, the
|
|
decoder, as part of its table may have effectivly made
|
|
certain of the variable fields in an instruction
|
|
constant. Separate functions for each of the
|
|
alternative values for what would have been treated as
|
|
a variable part can be created.
|
|
|
|
o use cache struct directly.
|
|
|
|
When a cracking cache is present, the semantic
|
|
functions can be generated to either hold intermediate
|
|
cache values in local variables or always refer to the
|
|
contents of the cache directly. */
|
|
|
|
|
|
|
|
extern insn_handler print_semantic_declaration;
|
|
extern insn_handler print_semantic_definition;
|
|
|
|
extern void print_idecode_illegal
|
|
(lf *file,
|
|
const char *result);
|
|
|
|
extern void print_semantic_body
|
|
(lf *file,
|
|
insn *instruction,
|
|
insn_bits *expanded_bits,
|
|
opcode_field *opcodes);
|
|
|