Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About vb99

  • Rank
  1. Yes, the result is fine (if I remember rightly), but the data in bank 0 gets corrupted because when __mul_32u__0000F_1_i is cleared, it is in the wrong bank (it should be in bank 1). The assembly looks like this: __mul_32u__0000F_arg_a EQU 0x0000007C ; bytes:4 __mul_32u__0000F_arg_b EQU 0x000000A0 ; bytes:4 __mul_32u__0000F_1_i EQU 0x000000A4 ; bytes:1 test_00000 ; { test ; function begin MOVF test_00000_arg_multiplicand, W BSF STATUS, RP0 ;bank 1 MOVWF __mul_32u__0000F_arg_b CLRF __mul_32u__0000F_arg_b+D'1' CLRF __mul_32u__0000F
  2. Bug description: Incorrect bank used in unsigned long multiplication under certain circumstances. Steps to reproduce: This has been seen when __mul_32u__0000F_arg_a is in bank 0, and __mul_32u__0000F_arg_b and __mul_32u__0000F_1_i are in bank 1. In the compiled code, in the calling function, bank 1 is selected, __mul_32u__0000F_arg_b is set up, bank 0 is selected, __mul_32u__0000F_arg_a is set up, and __mul_32u__0000F is called while still in bank 0. __mul_32u__0000F assumes that it is already in bank 1 on calling, clears __mul_32u__0000F_1_i, then clears RP0 (although it is already
  • Create New...