![]() |
Compiling with --enable-break behaves different (*solved*) - Printable Version +- Forum (https://www.boriel.com/forum) +-- Forum: Compilers and Computer Languages (https://www.boriel.com/forum/forumdisplay.php?fid=12) +--- Forum: ZX Basic Compiler (https://www.boriel.com/forum/forumdisplay.php?fid=11) +---- Forum: Bug Reports (https://www.boriel.com/forum/forumdisplay.php?fid=15) +---- Thread: Compiling with --enable-break behaves different (*solved*) (/showthread.php?tid=834) |
Compiling with --enable-break behaves different (*solved*) - Luzie - 01-05-2018 When I´m compiling this sample.bas from Einar Saukas Download/Info at: https://spectrumcomputing.co.uk/index.php?cat=96&id=30005 Downloads: JOY_SourceCode.zip (containing joy.asm) and: JOY_BorielZXBasicLibrary.zip (containing sample.bas and joy.bas) with --enable-break the program behaves different to compiling without --enable-break I´m tested on ZXB v1.7.1 (Windows) as Download-Page for v1.8.0 seems to be not accessible at the moment of writing) and SpecEmu-Emulator. Screenshot without --enable-break (Please scroll down over Picture to see complete screen) ![]() Screenshot with --enable-break (Please scroll down over Picture to see complete screen) ![]() Re: When compiling with --enable-break program behaves diffe - boriel - 01-06-2018 Will test it. Check you have the latest version 1.8.0 (now it's available) as it fixes some things with -O3 and other code generation. Which optimization level are you using? -O3? Re: When compiling with --enable-break program behaves diffe - Luzie - 01-07-2018 I tried with v1.8.0. I didn´t use the Optimizer-Option. Now I tested with -O2 and -O3 , but this makes no difference. Regards, Luzie Re: When compiling with --enable-break program behaves diffe - boriel - 01-23-2018 Okay, I think I've fixed it. Can you download this 1.8.1-beta version (for windows), and tell me if it works, please? :roll: Re: When compiling with --enable-break program behaves diffe - Luzie - 01-24-2018 boriel Wrote:Okay, I think I've fixed it.Yes! Bug is gone with v1.8.1-Beta. Compiles and runs OK (even with -O3). Thank you! |