| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
gp 'go privilege' starts execution until the privilege mode
changes. This can be used to break on task switches. I.e on m68k,
one could do:
gp { ~sr & 0x2000 && crp_aptr == 0x1234567 }
which would execute until the privilege mode changes to user mode and
the CPU root pointer is 0x1234567.
for cpu code, all that is needed to make this work is calling
debugger_privilege_hook() when the execution level changes.
|
|
|
|
|
|
|
| |
mode (nw)
NOTE1: namcos22 propcycl always pedals backwards now, will resolve in next commit.
NOTE2: diexec.h MAX_INPUT_LINES had to be increased, even without this commit m37710 was already more than 32 input lines.
|
| |
|
| |
|
| |
|
|
|
|
| |
m_vblank_interrupt_screen a finder. Indeed, the need for it should be removed from diexec entirely. nw
|
| |
|
|
|
|
| |
(nw)
|
| |
|
| |
|
|
|
|
|
|
| |
- PULSE_LINE is no longer a value. Existing uses have been changed to pulse_input_line with attotime::zero as the second argument.
- Formerly only INPUT_LINE_NMI and INPUT_LINE_RESET were allowed with PULSE_LINE. INPUT_LINE_NMI no longer receives special handling; instead, CPU devices must specify which of their input lines are edge-triggered and thus may be used with zero-width pulses by overriding the execute_input_edge_triggered predicate. INPUT_LINE_RESET is still special-cased, however.
- execute_default_irq_vector now allows a different default vector to be specified for each input line. This added flexibility may or may not prove useful.
|
|
|
|
| |
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
|
|
|
|
|
|
| |
* destaticify initializations (nw)
* fix this->set_screen (nw)
|
|
|
|
| |
ideally shouldn't) be used explicitly now (nw)
|
|
|
|
|
|
| |
min_cycles (nw)"
This reverts commit 46bad5c707cadd5293828f78d1bcbbb0ae23749c.
|
|
|
|
| |
(nw)
|
|
|
|
| |
device_execute_interface::pulse_input_line (nw)
|
|
|
|
|
|
|
|
|
|
|
| |
* move rarely-used output and pty interfaces out of emu.h
* consolidate and de-duplicate forward declarations, also remove some obsolete ones
* clean up more #include guard macros
* scope down a few more things
(nw) Everyone, please keep forward declarations for src/emu in src/emu/emufwd.h -
this will make it far easier to keep them in sync with declarations than having
them scattered through all the other files.
|
|
|
|
|
|
|
|
|
|
|
|
| |
* New abbreviated types are in osd and util namespaces, and also in global namespace for things that #include "emu.h"
* Get rid of import of cstdint types to global namespace (C99 does this anyway)
* Remove the cstdint types from everything in emu
* Get rid of U64/S64 macros
* Fix a bug in dps16 caused by incorrect use of macro
* Fix debugcon not checking for "do " prefix case-insensitively
* Fix a lot of messed up tabulation
* More constexpr
* Fix up many __names
|
|
|
|
|
| |
Use standard uint64_t, uint32_t, uint16_t or uint8_t instead of UINT64, UINT32, UINT16 or UINT8
also use standard int64_t, int32_t, int16_t or int8_t instead of INT64, INT32, INT16 or INT8
|
| |
|
|
|
|
| |
confusion (nw)
|
| |
|
| |
|
|
|
|
| |
(illogically) device_execute_interface (nw)
|
|
|
|
|
|
|
| |
SHA-1: 1f90ceab075c4869298e963bf0a14a0aac2f1caa
* tags are now strings (nw)
fix start project for custom builds in Visual Studio (nw)
|
|
|
|
| |
This reverts commit 5f19489cd2d0cd0b65ac250ac4b76d666a50509c.
|
| |
|
|
|
|
| |
fix start project for custom builds in Visual Studio (nw)
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
to eliminate device().machine().scheduler() chains all over the place (nw)
This change has been sitting in my local tree for months, from when I was
(mostly unsuccessfully) working on c64 performance. It gives a small speedup
to drivers with many tightly-interleaved executing devices (i.e. Commodore
drivers) I didn't think it was worth making everyone do a clean build for
such tiny gains but I didn't have the heart to chuck it. Since I'm already
making another core-touching, clean-build-needed commit tonight, in it goes.
|
| |
|
| |
|
|
|
|
| |
MCFG_CPU_IRQ_ACKNOWLEDGE_DRIVER/DEVICE (nw)
|
| |
|
| |
|
|
|
|
| |
to new license tagged form.
|
|
|
|
| |
deprecated / reduced the DEPRECATED noise a bit for now nw)
|
|
|
|
| |
added ATTR_DEPRECATED / flag some stuff in diexec.h as deprecated (nw)
|
| |
|
| |
|
| |
|
|
|
|
| |
MCFG_{CPU|DEVICE}_PERIODIC_INT_REMOVE to properly remove non-legacy VBLANK interrupts - the current code only reset the legacy interrupt which wasn't set anyways
|
|
|
|
|
|
| |
- updated device_execute_interface::interface_post_reset so screen is searched
from same context
- removed tilelgcy.h since no more users exist
- made bfm_adr2 a device
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
owner device, not the device itself, to make it consistent with devcb2
patterns. This change is mostly hidden since most drivers use
MCFG_DEVICE_VBLANK_INT_DRIVER and MCFG_DEVICE_PERIODIC_INT_DRIVER. But
for those few cases where a device was explicitly specified, it reduces
the awkwardness.
We should probably standardize this when using device_delegates for
consistency.
A full rebuild is necessary after taking this change, since the macros
mentioned above have changed their parameters.
|
|
|
|
| |
suspended and restarted on clock change. Note that the device still needs to have a clock before MAME actually starts executing timeslices.
|
| |
|