| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
| |
* added palcode disassembly
* added standard pseudo-opcode forms
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
start to customize disassembly and execution
|
| |
|
|
|
|
|
|
|
|
| |
* replaced memory accessors
* implemented tlb and address translation
* corrected exception vector logic
* improved cache isolation behaviour
* comments/formatting
|
|
|
|
| |
functions to tell to another person who spent minutes trying to find the functions, and we refer to such functions as swapping just about everywhere else in the codebase, nw
|
| |
|
|
|
|
| |
mcs96d.cpp: Minor spacing fix (nw)
|
|
|
|
|
|
| |
CALLF (nw)
unidasm: Konami CPU is big-endian (nw)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* hphybrid: major overhaul to add the 09825-67907 variant
* hphybrid: adapted hp64k & hp9845 to revised hphybrid CPUs
* hp9825: first release of HP9825B emulator
* hphybrid: added 09825-67907 to unidasm
* hp9825: improved appearance of blinking cursor
* hphybrid: minor changes
|
|
|
|
|
|
|
| |
When parsing an enumerated option, we should use the parameter of the
enumerated value, as an integer, instead of the raw identifier as a
string. The behaviour probably changed around commit b60879e595, but
modules still expect the old behaviour.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
* start looking at the extra opcodes in the SSD 2000 type XaviX chip (seems some undocumented 6502 opcodes are replaced with more custom ones)
* (nw)
* the xavix memory mapping gets stranger with each piece of new evidence (nw)
|
| |
|
|
|
|
| |
extricate emu.h from tools (nw)
|
|
|
|
|
|
| |
* Move around the debugger hooks to get a small but measurable performance increase
* Remove emucore from external tools
* Improve performance of DSP16 interpreter a little by generating six variants of execution loop
|
| |
|
|
|
|
| |
optimisation opportunities (nw)
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* create derived 6502 type for XaviX because it has at least one custom 4-byte opcode that doesn't fit any other type.
treating that opcode as NOP for now.
have a feeling it might be something to do with the other integrated hardware, might be 'execute co-processor code chain at this address' or something similar
It isn't a standard JSL (Jump Subroutine Long) like the SNES cpu opcode in the same place as this, it seems to point at some code-like structures tho)
could also be a secondary operation mode with different encoding like ARM's Thumb mode tho I guess.
We currently only have a single XaviX based dump (taitons1) but there are more on the way. I'm going to see if the code flow makes any sense at all with these missing, or if any of it gives a clue as to what they should actually do.
* xavix - let's call these callf and retf then
after further investigation these are some kind of extra 'long jump' subroutine / task handlers, the 0x80 also being a custom opcode was throwing me off trying to identify them before.
looks like they might have been hacking 65816 features into the regular 6502 core?
* prepare for extra address bits (nw)
* better program flow (nw)
|
|
|
|
| |
tabulation, clean .hsi as xml (nw)
|
|
|
|
|
|
|
|
|
|
| |
* tools/imgtool/filtbas.cpp: fixed Coverity "Identical code for different branches" warning (nw)
* mame/video/decbac.cpp: fixed Coverity "Identical code for different branches" warnings (nw)
* Revert "mame/video/decbac.cpp: fixed Coverity "Identical code for different branches" warnings (nw)"
This reverts commit bdc1761996b8ead3ee7b0233a41ad0eff6f58311.
|
|
|
|
|
|
| |
- Separate disassembler for i802x (including unemulated 8022 instructions)
- Provide separate (though mostly just more limited) 8021 opcode table
- Writes to 8021 P0 no longer go through memory space
|
|
|
|
|
|
|
|
|
|
| |
* lib/util/chdcd.cpp: fixed Coverity "Resource Leak" warning (nw)
* src/lib/util/chdcd.cpp: fixed more Coverity "Resource Leak" warnings (nw)
* tools/imgtool/modules/mac.cpp: fixed Coverity "Resource Leak" warnings (nw)
* devices/bus/ti99/gromport/cartridges.cpp: fixed Coverity "Resource Leak" warning (nw)
|
| |
|
|
|
|
| |
or direct)
|
|
|
|
|
| |
please people, remember to keep source UTF-8 and if you're committing on behalf of others, clean up indents to meet MAME conventions
anyone can run srcclean over a submission and see what will get hit
|
|
|
|
| |
This reverts commit 54155441e9ba9941e85d80c4834a66376a11e791.
|
|
|
|
|
| |
This reverts commit f537428e5a40ba6dde8ca9bf0fe9ae6b1f189ac4, reversing
changes made to 0d70d798107d4e4e8fb9f230410aeb1e888d65c5.
|
| |
|
|
|
|
| |
7.2.0) (nw)
|
|
|
|
|
|
|
|
| |
Disassemblers are now independant classes. Not only the code is
cleaner, but unidasm has access to all the cpu cores again. The
interface to the disassembly method has changed from byte buffers to
objects that give a result to read methods. This also adds support
for lfsr and/or paged PCs.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(#2263)
* Created a more flexible imgtool::datetime structure for use within Imgtool
This is intended to replace most usage of time_t
* Changing the granularity of imgtool_clock from 1ms to 100ns, as per Vas' suggestion
* Created arbitrary_datetime in timeconv.h to facilitate interpretation of datetime info
I concluded that invoking std::mktime on manually assembled std::tm is bad, because it is indeterminate how the std::tm members may be "dominant". This required that I go further in imgtool, and update a number of drivers and eliminate the parameter of imgtool::datetime that takes std::tm.
|
| |
|
| |
|