summaryrefslogtreecommitdiffstatshomepage
path: root/src/emu/sound/fmopl.c
diff options
context:
space:
mode:
author Aaron Giles <aaron@aarongiles.com>2008-07-24 06:18:01 +0000
committer Aaron Giles <aaron@aarongiles.com>2008-07-24 06:18:01 +0000
commit9b63c422030b302154ad57541ccc5375cdc7e215 (patch)
tree6b044748b88c9a24c916e7c8042462ece99f5f96 /src/emu/sound/fmopl.c
parent0865f72a9a1a0150c1320dad2c5940fd736bc640 (diff)
From: Atari Ace [mailto:atari_ace@verizon.net]
Subject: [patch] .data removals to fix reset/multisession bugs Hi mamedev, One nice artifact of properly constifying data structures in MAME is that it makes it relatively easy to spot a class of reset/multisession bugs, namely that almost any object in .data is probably in error. Unless the value is properly initialized in a reset routine the initial non-zero value can't be relied upon, so there's no need to have a non-zero value to begin with. With that in mind, here's a patch to move more items out of .data by either applying const, removing the non-zero initializer (if its overwritten by init/reset) or by adding appropriate initialization code. In most cases I tried to add initialization code to a reset routine, but in some cases I chose an init routine, possibly leaving a reset bug intact. Some interesting bits: 1. tms9900 core. The use of .data to initialize the irq_level wasn't correct in some cases as the layout of the structure was core dependent. 2. bfcobra.c. By introducing a VIDEO_START routine a hack in VIDEO_UPDATE could be removed. ~aa
Diffstat (limited to 'src/emu/sound/fmopl.c')
0 files changed, 0 insertions, 0 deletions