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
Address.cs
Asm65.csproj
CharEncoding.cs
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
Label.cs
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
OpName.cs
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