Andy McFadden ba35f88d02 Mark flags as indeterminate for inline BRK ... We weren't altering the status flags after a BRK because of the assumption that a BRK was a crash. For an inline BRK, such as a SOS call, execution continues. We need to mark NVZC indeterminate or we may incorrectly handle conditional branches that follow. The BRK instruction now uses the same flag updater as JSR, since it's effectively a subroutine call to unknown code. If execution doesn't continue across the BRK then the flags don't matter. Updated 20182-extension-scripts to exercise this.		2020-08-22 08:56:38 -07:00
..
Properties	Initial file commit	2018-09-28 10:05:11 -07:00
Address.cs	Initial file commit	2018-09-28 10:05:11 -07:00
Asm65.csproj	Initial file commit	2018-09-28 10:05:11 -07:00
CharEncoding.cs	PETSCII does DCI	2019-08-20 17:55:12 -07:00
CpuDef.cs	Tweak M/X/E flag handling	2020-07-06 08:31:18 -07:00
Formatter.cs	Make operand wrap length configurable	2020-07-19 18:39:27 -07:00
Helper.cs	Add junk/align directives	2019-10-18 21:00:28 -07:00
Label.cs	Label rework, part 1	2019-11-08 21:02:15 -08:00
Number.cs	Data Bank Register management, part 2	2020-07-09 11:14:55 -07:00
OpDef.cs	Mark flags as indeterminate for inline BRK	2020-08-22 08:56:38 -07:00
OpDescription.cs	Clarify BRK explanation	2019-10-29 10:18:48 -07:00
OpName.cs	Rename undocumented 6502 opcodes to match Unintended Opcodes doc	2018-10-05 14:28:45 -07:00
StatusFlags.cs	Fix application of reloc info in data areas	2020-07-07 11:48:51 -07:00
StringOpFormatter.cs	Make operand wrap length configurable	2020-07-19 18:39:27 -07:00
TriState16.cs	Initial file commit	2018-09-28 10:05:11 -07:00