HI-TECH PICC Release Notes for Version 8.05PL2

HI-TECH PICC Release Notes for
Version 8.05PL2
27th September 2004
THIS FILE CONTAINS IMPORTANT INFORMATION RELATING TO THIS
COMPILER. PLEASE READ IT BEFORE RUNNING THIS SOFTWARE.
Description
This is a minor patch-level update from the 8.05PL1 release. All reported bugs have
been fixed and comprehensive tests have been carried out to further improve code reliability.
Previous Version
The previous version was 8.05PL1, released August 2004.
New Features
General
New chips added (8.05) PICC now has support for the following devices: 10F200,
10F202, 10F204, 10F206, 12F508, 12F509, 12F635, 12F683, 16C557, 16F505,
16F54, 16F57, 16F636, 16F688, 16F716, 16F737, 16F747, 16F767 and 16F777.
New chipinfo entry (8.05) Three new entries have been added for chips in the PICC
chipinfo INI file. The entries are FLASHTYPE, EEPROMSIZE and DATABANK and
relates to the type of flash and EEPROM memory the device has. This information
allows the compiler to more accurately select appropriate library routines.
Updated bootloader (8.05) The 16F87x bootloader has been updated to accommodate
higher baud rates. It is also now easier to build and use.
Bootloader Project Files (8.05PL1) Project files are now included for building the
bootloader under MPLAB. Also included are pre-compiled versions of the bootloader
and sample application.
1

New Sample Code (8.05PL1) A new sample program designed to run on the PIC-
DEM2 plus demo board is now included in the compiler’s samples directory.
Driver
New option (8.05) An option has been added to allow more control over the RAM
usage in a project.
• The -BANKCOUNT=number option allows the user to specify the number of
RAM banks used in a project. Normally the compiler will assume that all
RAM banks of the processor may have been used. If the user can assure that
the compiled program doesn’t require all of the banks, then the compiler
can perform additional code size optimizations. This is particularly useful
to processors that have four RAM banks but two of the banks only contain
SFR’s (16F72/73/74, 16F870/871/872/873/874, etc...). The allowable bank
counts are: 1,2,3 or 4.
Code Generator
New optimizations (8.05) An additional optimization has been added to the code generation
stage of the compiler.
Assembler
• Additional code size optimizations may be done for processors that have
four RAM banks but only two are available for general purpose RAM.
New optimizations (8.05) New optimizations have been added to the assembler stage
of the compiler. These optimizations will only become apparent when the assembler
optimizer is enabled.
Changes
Release notes
• There has been improvements to an optimization which will attempt to convert
two bit clear on status instructions (bcf) to a single clear file register
(clrf) instruction.
• A new function inlining optimization has been implemented. This optimization,
if efficient to do so, will attempt to inline small functions rather
than call them. When applied, this optimization has the potential to reduce
stack usage and/or code size.
Readme and bugfixes files (8.05) The readme and bugfixes files have been merged
into a single (README) file and contains more detailed information about the release.
2

Header files
Changes for flash and EEPROM macros (8.05) Previously the flash and EEPROM
access macros and function definitions for each chip were defined in that chip’s
specific headerfile, this is no longer the case. As well as the existing EEP-
ROM_SIZE definition, the preprocessor will now define a symbol to indicate
what type of flash access it uses. In pic.h the combination of the FLASH and
EEPROM symbols will determine what sort of access macros to provide.
PICINFO.INI file
12F635 ICD ranges (8.05PL1) The reserved memory locations required for using the
ICD2 with the 12F635 has been updated in accordance with the latest Microchip
documentation.
HPDPIC
No longer supported (8.05) The text-based IDE HPDPIC will no longer be supported.
It will still be included with the compiler and it still works, however some some
processors cannot be selected, the compiler’s string packing feature is disabled
and the EEPROM read/write library routines will not automatically be included
if called.
Limitations
Demo Mode
Disabled options After installtion this version of the compiler will run in demo mode.
When operating in demo mode, compilation of programs will be slower then
normal and some command-line options are disabled. The following is a list of
the disabled options:
• -D to predefine macro symbols
• -L to specify libraries to be scanned by the linker
• -L-opt to allow specification of additional linker options
• -M map file generation
• -NORT to disable runtime code inclusion
• -PRE to only preprocess source files
• -RESRAM to reserve RAM ranges
• -RESROM to reserve ROM ranges
• -U to undefine macro symbols
• -V for verbose compilation messages
The compiler will continue to operate in demo mode for 21 days, after which it will
cease to function. If you have purchased this compiler, these limitations may be removed
by running the activation program. Visit HI-TECH Software’s web site for
further details about activation/registration.
3

Preprocessor
Incorrect result for sizeof The result of the sizeof preprocessor operator when applied
to a pointer will always return 1. Use of the C sizeof operator will return
the correct value.
Parser
Missing parenthesis not detected A missing end parenthesis is not detected in variable
declarations when the variable is type cast. For example,
static char C @ ((unsigned)&PORTA;
This problem does not appear to affect any output code, but may cause problems
when using third-party software tools.
Qualified arrays generate error The compiler generates an error when compiling
complicated qualified arrays, e.g.:
const char * const * const listnames[] = {menu0, menu1};
The error is not issued if the array is not qualified, or for arrays of more basic
types.
Structure initialization Locally defined structures cannot be initialized.
Code Generator
Functions returning ROM structure For Highend devices (17Cxxx), a function cannot
return a copy of a structure which resides in ROM.
Indirect function calls For Highend devices (17Cxxx), certain indirect function calls
with more than one byte of argument may produce incorrect code.
Functions as arguments to printf The argument list to printf or sprintf should not
include function calls. For example,
printf(“x = %f, sin(x) = %f\n”, x, sin(x*3.141592/180.0));
This code demonstrates a workaround:
y = sin(x*3.141592/180.0);
printf(“x = %f, sin(x) = %f\n”, x, y);
Error on initialization of complex bitfields Any structure using bitfields within a structure
or union cannot be initialized. For example, using the following types where
a structure is a member of a union, initialization of the structure’s bitfields will
generate an error.
4

typedef struct {
unsigned b0:1, b1:1, b2:1, b3:1, b4:1, b5:1, b6:1, b7:1
} byte_bits;
typedef union {
byte_bits bits;
char byte;
} byte_or_bits;
This will generate a compiler error:
byte_or_bits example = { {1,0,1,1,0,1,0,0 } };
Instead, use a single value:
byte_or_bits example = { 0b10110100 };
Multiple block variable declaration Functions which have variables declared within
multiple blocks where code within the block requires the use of temporary memory,
may get corrupted when compiled with global optimizations. A workaround
is to move the inner variable declaration outsize of the block.
Libraries
Minimum floating point value The floating point math libraries cannot perform operations
predictably on numbers below the order of 1e-35. The result is either
correct or zero.
Bug Fixes
The following are descriptions of bugs that were present in the previous versions of
this compiler, and which have been fixed in this release.
Driver
Crash linking many files (8.05PL1) For projects with greater than 100 files, the driver
may crash at the link stage. The driver has been updated to account for projects
of this size.
Preprocessor
Warning level ignored (8.05PL1) The -W warning level option was ignored by the
preprocessor which resulted in some warning not being shown. This has been
corrected.
5

Preprocessor crashes scanning macros (8.05) A problem with the preprocessor may
cause it to crash when processing macros which have trailing parenthesis missing.
The preprocessor has been altered so as to produce an error message if the trailing
parenthesis is omitted.
Preprocessor crashes on macros functions (8.05) A problem with the preprocessor
may cause it to crash when processing macros which take parameters but were
called with the wrong number of parameters.
The preprocessor has been altered so as to produce an appropriate error message.
Preprocessor treats constants as signed (8.05) The preprocessor incorrectly treats all
constants as signed values. This may lead to unexpected results if using the preprocessor
to compare values. For example #if 1 > 0xFFFFFFFF should be a
false condition if the second operand is treated as unsigned, but true if treated as
signed.
The preprocessor has been fixed to follow the ANSI standard. Values are considered
to be 32-bit values by the preprocessor.
Parser
Crash on missing comma (8.05) A problem in the parser (P1) may cause it to crash
when parsing an enumerated type definition that has a missing comma between
enumerators in the list.
The parser will now generate an error if such a condition is encountered.
Crash on missing union tag (8.05) If a variable declaration is performed using a union
tag that is yet to defined, the parser may crash. For example: union tag var =
{1}; // tag not yet defined
The parser has been changed to handle this correctly.
Hang on missing specifier (8.05) In some instances calls to printf functions where the
parameter was given but no specifier caused the parser to hang. For example:
sprintf(buffer,”The number is”,number);
The parser will now generate an appropriate error message.
Error given for LU suffix (8.05) The parser generates an error when encountering
constants with an LU suffix.
This syntax is now accepted.
Code Generator
Variable argument functions not returning (8.05PL2) For baseline (12bit) processors,
functions that are not qualified as fastcall and which have a variable number
of arguments (...) may not return. Printf is such a function and runs correctly,
but never returns. Such functions now work as expected.
6

IRP bit selection after call (8.05PL2) When an XOR, OR or plus operation occurred
on a char object which required to be accessed indirectly following a function
call in which the IRP bit was modified, the result may incorrectly be assigned to
the wrong bank. This has been fixed.
IRP bank selection bit corruption (8.05) A problem in the code generator lead to the
IRP bank selection bit possibly getting corrupted over a function call. The problem
only manifested itself when assembler optimizations were applied.
The code generator now assumes the IRP bit may get corrupted over a function
call and ensures it is set correctly after the call.
Incorrect bank selection after if (8.05) The wrong bank may get selected for midrange
PICs with four banks after an if statement that tests bit object in different
banks. For example:
int i;
if ((RCIF & RCIE)|(TXIF & TXIE))
++i;
--i; //possible wrong bank selection here
The problem has now been fixed.
Assembler
SET/EQU (8.05PL1) Added code to test that SET or EQU doesn’t have the same name
as a macro.
Bank select problem (8.05PL2) An assembler optimization problem caused the wrong
bank to be selected in some instances where an assembler level label had multiple
paths of arrival where each path had a different bank selected. This typically
happened where there are many comparisons in a row (eg: switch statements,
multiple if comparisons) followed by access to an object in a bank other than
bank0, followed by a return. This has been fixed.
Wrong bank selected (8.05PL1) A bank selection problem may occur in code which
uses many ’if’ statements in a row, which tested bit objects. This tends to affect
code which is typically written for interrupt routines and therefore may result in
some ’if’ statements evaluating incorrectly. This problem has been fixed.
Crash with assembler optimizations (8.05) With the assembler (ASPIC) optimizers
enabled, certain very specific sequences of code caused the assembler to crash.
This problem is quite rare and did not affect generated code if the assembler ran
to normal completion.
This problem has now been fixed.
7

Cromwell
Erroneous output on complex return types (8.05) For some functions which use a
complex return type (structure/union pointers) the COF file output may be incorrect.
This problem has been fixed.
Header Files
Missing SSPIE definition (8.05PL2) The SFR definition for SSPIE was missing for
the 16C774 processor. This has now been added.
Incorrect SFR addresses (8.05PL1) Some of the SFR definitions in the PIC16F87.H
header file were incorrect. This affected their use on the PIC16F87 and PIC16F88
processors. This has now been corrected.
Typo in 16F7x7 header (8.05) There was a typo in the pic16f7x7.h header file which
resulted in some SFRs not being defined correctly. This has been updated.
PICINFO.INI file
Incorrect ICD2 reservations (8.05PL2) The memory ranges required to be reserved
when using the MPLAB-ICD2 on the 16F688 or 12F683 was not correct. This
has been adjusted.
Insufficient RAM definition (8.05PL1) The RAM definition for bank 0 of the 16F636
was less than it should have been. This may have resulted in the compiler giving
an out of space error earlier than expected. The correct RAM range has now
been added.
Missing RAM definition (8.05PL1) The RAM definition for bank 2 of the 16F688
was missing. This definition has now been added.
Incorrect EPPROM size (8.05PL1) The value of the pre-processor define EEPROM_SIZE
which is obtained from the PICINFO.INI file was incorrect. This has been adjusted
to the correct values.
Incorrect RAM ranges (8.05) The RAM ranges given for the rf12F675 (ie, 12F675F/H/K)
was incorrect.
Library Code
Floating point calculations (8.05PL2) The library routines ldexp, sqrt, exp, pow,
sinh, cosh & tanh in some instances would erroneously return values of zero.
This has been corrected.
Leap year day incorrect (8.05PL1) The day of the week calculated for February 29th
which is generated by the time functions (ctime) was incorrect. This has now
been corrected.
8

Floating point exponent (8.05PL1) The exp() and ldexp() routines did not correctly
do bounds checking where the exponent may overflow. This meant that
caclulations that overflowed returned a result which is significantly incorrect.
These routines now check the limits and will return a maximum value or zero
where appropriate.
Undefined symbol for string packing (8.05PL1) The 16F87 and 16F88 processors,
although capable of the string packing optimization, were not getting the correct
library routine linked in to handle it. This would result in an undefined symbol
uses_packed_strings.
The correct library is now linked accordingly.
Incorrect results for 32-bit doubles (8.05) Some four-bank processors were not getting
the correct library routine linked which resulted complex assignments (+=,-=,*=,/=)
involving objects in bank 2 and 3 to give incorrect results.
The correct library is now linked accordingly.
Incorrect results for atof() and strtod() (8.05) A problem in strtod() (atof() shares
code with this function) may cause an incorrect result if there are leading zeros
specified with the exponent. Only the first two digits of the exponent were read
so that code similar to atof("1.7546e003") will return a value with incorrect
exponent.
The source for this function has been corrected and new libraries compiled.
Updates
Monitor the announcements forum on HI-TECH Software’s web site for information
relating to new versions or patches, and/or subscribe to our announcement mailing list
- send email to HI-TECH Software’s mailing list for more information.
9