Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

lwriter.cpp: Reimplement the 0x600000-0x7fffff range to bitwise-OR on write. #8315

Merged
merged 1 commit into from
Jul 19, 2021

Conversation

jrmuizel
Copy link
Contributor

This appears to be the desired effect of the code using this range.
It fixes the rasterization of the '5' glyph in the test page and avoids
the "Fatal system error @ 0x2a8416" buffer overflow in glyph the cache
when writting out the last byte of the bitmap because it ends up or'ing
with zero instead of overwritting with zero.

Fixes #8309

Copy link
Member

@cuavas cuavas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please note the affected driver in your commit messages and PR titles – a person reading commit history shouldn’t need to dig into diffs to get context.

Also, while you’re doing this, you could change m_dram_ptr to a required_shared_ptr<uint16_t> and change m_rom_ptr to a required_region_ptr<uint16_t> – this makes the code a bit clearer and helps avoid certain common bugs.

src/mame/drivers/lwriter.cpp Outdated Show resolved Hide resolved
src/mame/drivers/lwriter.cpp Outdated Show resolved Hide resolved
@jrmuizel jrmuizel changed the title Reimplement the 0x600000-0x7fffff range to bitwise-OR on write. lwriter: Reimplement the 0x600000-0x7fffff range to bitwise-OR on write. Jul 19, 2021
@jrmuizel jrmuizel changed the title lwriter: Reimplement the 0x600000-0x7fffff range to bitwise-OR on write. lwriter.cpp: Reimplement the 0x600000-0x7fffff range to bitwise-OR on write. Jul 19, 2021
… write.

This appears to be the desired effect of the code using this range.
It fixes the rasterization of the '5' glyph in the test page and avoids
the "Fatal system error @ 0x2a8416" buffer overflow in glyph the cache
when writting out the last byte of the bitmap because it ends up or'ing
with zero instead of overwritting with zero.

Fixes mamedev#8309
@rb6502 rb6502 merged commit 0c20873 into mamedev:master Jul 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

lwriter has "Fatal system error @ 0x2a8416" when running text drawing code
3 participants