E-LAB Computers
 

Eingrenzung eines Merlin-Errors

... oder wo passierts ...

jomixl
Benutzer
Avatar
Geschlecht:
Beiträge: 234
Dabei seit: 02 / 2008
Betreff:

Eingrenzung eines Merlin-Errors

 ·  Gepostet: 13.04.2018 - 09:02 Uhr  ·  #1
Hallo zusammen,
ich musste ein altes Mega16 Programm erweitern und bin jetzt fast an der Flash-Grenze.
Darum hab ich mal den Optimizer probiert. Der schafft zwar ca. 30% Platz aber dafür läuft das Programm auch nicht mehr. Nun will ich versuchen das Problem einzugrenzen.
Das Programm besteht aus mehreren Units und ich hab keinen Plan wie ich jetzt vorgehen soll.
Hab bisher auch keinen Schalter gefunden mit dem ich ein Unit vom Optimizer sperren kann oder hab ich da was übersehen?

Danke für eure Vorschläge
Gruß Joachim
Merlin
PowerUser
Avatar
Geschlecht:
Alter: 26
Beiträge: 1502
Dabei seit: 03 / 2005
Betreff:

Re: Eingrenzung eines Merlin-Errors

 ·  Gepostet: 13.04.2018 - 11:11 Uhr  ·  #2
Hi Jachim.

The optimiser transcends units, so omitting units makes no sense. I have a whole range of options to narrow things down. The attached are in English, I am afraid, but describe how the problem can be narrowed. If you know roughly where the error lies (e.g. in a particular function) you can send the asm and dsm files to me straight away and I will look to see if I can see anything obvious.

There is also a new version of optimiser about to be released this weekend which resolves a few small issues. Again if you send me the asm and dsm files via pm I will run your program against the new version and see if your program is affected.

Regards

Merlin.
Anhänge an diesem Beitrag
Disabling parts of the optimiser

Each part of the optimiser can be separately disabled using flags. This is to help isolate issues that might be difficult to find otherwise. It should not be used for 'production code'.

Each flag is of the form

{$OPTI xxx}

To isolate the part of the optimiser causing the problem, put the following lines at the top of your main code.

{$OPTI NO_REDUNDANT_FRAME_USAGE_OPT}
{$OPTI NO_OPT_OFFSET_LOADS}
{$OPTI NO_CHECK_REDUNDANT_LOAD}
{$OPTI NO_CHECK_REDUNDANT_FRAME_LOAD}
{$OPTI NO_CHECK_REDUNDANT_SAVE}
{$OPTI NO_CHECK_MOV}
{$OPTI NO_CHECK_RETURN_REGS}
{$OPTI NO_LOOP_OPT}
{$OPTI NO_OPT_LOOP_LOADS}
{$OPTI NO_BRANCH_OPT}
{$OPTI NO_CSE_OPT}
{$OPTI No_Remove_Code_Islands}
{$OPTI No_Opt_Final_MOV}
{$OPTI NO_COM_OPT}
{$OPTI NO_OPT_TST}
{$OPTI NO_BITTEST_OPT}
{$OPTI NO_OPT_CPI}
{$OPTI NO_CALL_FRAME_OPT}
{$OPTI NO_CALL_FRAME_OPT_LOCAL}
{$OPTI NO_OPT_LOCAL_VARS}
{$OPTI NO_OPT_LOCAL_VARS2}
{$OPTI NO_OPT_LOCAL_VARS3}
{$OPTI NO_ALLOW_INLINE}
{$OPTI No_Phase_4}
{$OPTI No_Phase_3}
{$OPTI No_Phase_2_OR_3}
{$OPTI No_Phase_1_2_OR_3}

This effectively disables every part of the optimiser, so a compile and optimise now should have the same effect as just compiling.

To reintroduce an optimisation comment out the line associated with that optimisation, for example

//{$OPTI No_Phase_1_2_OR_3}

or

{ $OPTI No_Phase_1_2_OR_3}
(note the space between { and $)

Reintroduce the optimisations one by one until the problem re-appears, and advise me of the results. I recommend reintroducing from the bottom upwards.

Merlin.
Dateiname: Disabling Optimiser Parts.txt
Dateigröße: 1.57 KB
Titel:
Heruntergeladen: 174
Special Debug Mode
==================

Where a problem proves very difficult to isolate, a special debug mode is available.

It will typically take about 10 tests to isolate the problem down to a small nuber of lines.

Add the line

{$OPTI SPECIAL_DEBUG}

to the source. Then compile and optimise as usual. Then test the result. Approximately half of the program will not be optimised.

Now compile and optimise again. This time you will see a new screen pop up asking whether the test failed or passed.

If it failed, the other half of the program will be tested. Typically it will pass, but of course the problem may exist in both halves.

Repeat the process, making a note of the result each time until the optimiser tells you that testing is complete. Each iteration will narrow the fault down to a smaller set of lines.

Then zip the sub-directory MERLIN_DEBUG and send to Merlin.
Dateiname: special debug mode.txt
Dateigröße: 907 Byte
Titel:
Heruntergeladen: 214
jomixl
Benutzer
Avatar
Geschlecht:
Beiträge: 234
Dabei seit: 02 / 2008
Betreff:

Re: Eingrenzung eines Merlin-Errors

 ·  Gepostet: 13.04.2018 - 11:46 Uhr  ·  #3
hi merlin,
thanks for your answer! I'll try to findout where the error occures.

joachim
allan
Benutzer
Avatar
Geschlecht: keine Angabe
Alter: 66
Beiträge: 11
Dabei seit: 10 / 2016
Betreff:

Re: Eingrenzung eines Merlin-Errors

 ·  Gepostet: 14.04.2018 - 15:55 Uhr  ·  #4
Hi Merlin!

Looks like the latest optimizer version 3.5.7.3 corrupts Dataflash SPI driver or something in FlashIO.pas
Something happens with DataFlash address, data is read from wrong location.

regards,
Allan
Merlin
PowerUser
Avatar
Geschlecht:
Alter: 26
Beiträge: 1502
Dabei seit: 03 / 2005
Betreff:

Re: Eingrenzung eines Merlin-Errors

 ·  Gepostet: 14.04.2018 - 16:28 Uhr  ·  #5
Hello Allen.

Thanks for letting me know. Could you send me an example asm and dsm files via pm.

Do you know if earlier versions exhibited this problem?

Thanks

Merlin.
Gewählte Zitate für Mehrfachzitierung:   0

Registrierte in diesem Thema

Aktuell kein registrierter in diesem Bereich

Die Statistik zeigt, wer in den letzten 5 Minuten online war. Erneuerung alle 90 Sekunden.