Please provide a list of unsolved bugs

[Dany]

Hi people of mE,

please see http://www.mikroe.com/forum/viewtopic.p ... 46&start=6
It is not about mikroPascal itself, but about the way of working regarding bugs and problems.

Recently I did loose a lot of time due to a compiler bug, and this could solve this problem.

Thanks in advance!

[anikolic]

Hi,
I've answered you here: http://www.mikroe.com/forum/viewtopic.p ... 424#112424 and updated the Unresolved Bugs List, as I have promised: http://www.mikroe.com/forum/viewtopic.php?t=22383

Best regards,
Aleksandar

[Dany]

Thanks!

[janni]

Hi Aleksandar,

As you already started the good work , could you add also minor problems? Like:

Code Explorer stops functioning if:

- a pointer to structure (variable or constant) is declared, for example:

Code: Select all

var ptrs: ^array[3] of byte;

- arithmetics is used in variable declaration at absolute address:

Code: Select all

var bb:  byte; absolute $80+9;

This was brought up already few times by different users.

It would be also useful for many users to know some features of the PIC compilers that are not exactly errors, but are not described in help, like:

- optimiser does not detect that variables are changed by indirect addressing (using FSR) which may lead to wrong results, like

Code: Select all

    w2:=0;
    FSR0Ptr:=@w2;
    INDF0:=INDF0+5;
    w2:=w2+1;           //w2=1 here

- function memcmp works correctly only for ASCII chars (i.e. values in 0..127 range),
- labels used in assembly have visibility limited to routines they're used in,
- Include directive removes line termination chars, so it cannot be used with asm blocks,
- used RAM indication does not take into account Rx registers, or ISR buffers for Rx registers and FSRx ones,
- not all variables are visible in Statistics (like buffers for internal registers and FSRx in ISR).

Maybe reactivation of Tips & Trics forum would be a good idea?

[anikolic]

Hi,
Thank you janni, we will consider all of your suggestion. You can expect this Unresolved Bugs List to regain it's full purpose.

Best regards,
Aleksandar

[janni]

I'm affraid there's a new one for the list . See here http://www.mikroe.com/forum/viewtopic.p ... 555#112555

[anikolic]

Done: http://www.mikroe.com/forum/viewtopic.p ... 579#112579

[janni]

Thanks, but that's mB forum - the problem is also present in mP PRO and not all of us check all forums...

[Dany]

Hi Aleksandar, sorry to bother you again with this...

Is there an updated list of resolved/unresolved mP bugs?
Both lists are very, very short and are surely not complete.

It is a pity that there are no reliable/complete lists. Also for the bèta testers this is a horror: they do not know what to test again if a new version is released...
I spent yesterday evening several hours to test all my observations against v3.80, not knowing if something was supposed to be done regarding them... A shame.

[anikolic]

Hello Dany,

Since the pressure for introducing the online bug tracking system builds up with time, we will definitely need to implement some convenient mechanism for this. Online bug tracking systems as Bugzilla are on the menu, but we haven't got the time to focus to this as a major priority. We have much ongoing activities and we are putting compiler development as our major priority, focusing more on IDE bugs and inconveniences.

So, patience is the key.

Best regards,
Aleksandar

[Dany]

Hello Dany,

Since the pressure for introducing the online bug tracking system builds up with time, we will definitely need to implement some convenient mechanism for this. Online bug tracking systems as Bugzilla are on the menu, but we haven't got the time to focus to this as a major priority. We have much ongoing activities and we are putting compiler development as our major priority, focusing more on IDE bugs and inconveniences.

So, patience is the key.

Best regards,
Aleksandar

Thanks! Keep up the good work!