CCS 4104 Compiler Bug!

monsters_inc · Joined: 18 Jan 2010 Posts: 14

Hi,
I use CCS 4104 PCWHD compiler with PIC24FJ256GA106.
When I use directive "#type unsigned" compiler replaces in code destination address of one BRA or CALL instruction with 0x20C wich produces PIC restart.
Function with BRA or CALL instruction with wrong destination address depends of code that I add or remove.
If I compile exact same code with v4093 or v 4099 everything is ok.
If I remove directive "#type unsigned" everything is ok with CCS v4104, but I need by default int8, int16 and int32 to be unsigned.
If I compile in debug mode with CCS v4104 everything is ok.

bkamen · Posted: Wed Feb 17, 2010 7:25 am

So when you declare your var's, use unsigned in their declaration.

Or make a type like MCHP does in all their code. (uppercase stuff like BYTE and WORD)

or uB or uW or uL

-Ben
_________________
Dazed and confused? I don't think so. Just "plain lost" will do. :D

Wayne_ · Joined: 10 Oct 2007 Posts: 681

Taken from the help

"Note: All types, except float, by default are unsigned; however, may be preceded by unsigned or signed. "

Notice, all types are unsigned by default anyway!

Ttelmah · Guest

This is one of those 'beware of the manual' bits.....

Unsigned, is the default, _unless_ he is running in ANSI mode. The manual has not been updated to reflect this (it is in the 'readme.txt' fo the compiler).
So for every other mode, "#type unsigned", is pointless, but for ANSI mode it is useful. Now 'oddities' with signed values on the latter chips, have been reported here in a number of other threads... :-(
I'd suggest trying in CCS4 mode, and switching the string handling to ANSI if required. Except then for the default integer sizes, this should be close to operating the same.

Best Wishes

Guest · Posted: Wed Feb 17, 2010 10:17 am

Hi, Wayne_, Ttelmah, For PCD compiler(PIC24, dSPIC) by default is signed:
Note: All types, except char, by default are signed; however, may be preceded by unsigned or signed (Except int64 may only be signed). Short and long may have the keyword INT following them with no effect. Also see #TYPE to change the default size.

This is from PCD.CHM.

Best Regards.

PCM programmer · Joined: 06 Sep 2003 Posts: 21708

CCS tried to make the data types for the PCD compiler be more like conventional C:

FvM · Joined: 27 Aug 2008 Posts: 2337 Location: Germany

The #type preprocessor command has generated unexpected side effects with some previous PCD versions, I stopped
using it since then. The special thing with the present bug is, that it has no reasonable explanation, so it's no clear,
if it generally depends on #type only. In any case, the bug has to be fixed by CCS.

PCD has considerably improved in the last 18 month since I'm using it. In the beginning I found several new bugs
each day. Now it's from time to time.

monsters_inc · Joined: 18 Jan 2010 Posts: 14

Hi. I added two more files with code to the project and found that the wrong destination addres of BRA, CALL instructions appear with or without directive "#type unsigned".

This is strange!

FvM · Joined: 27 Aug 2008 Posts: 2337 Location: Germany

monsters_inc · Joined: 18 Jan 2010 Posts: 14

There is nothing special in project. A lot of code for driving three serial ports, SPI and ADC. The strange thing is that always destination address is 0x20C and only on one BRA or CALL instruction!

FvM · Joined: 27 Aug 2008 Posts: 2337 Location: Germany

There seems to be something really attracting at address 0x20C. Perhaps you find out, what it is.

monsters_inc · Joined: 18 Jan 2010 Posts: 14

Address 20C doesn't exist in listing.

FvM · Joined: 27 Aug 2008 Posts: 2337 Location: Germany

monsters_inc · Joined: 18 Jan 2010 Posts: 14

Thanks for info FvM. I'll try.

monsters_inc · Joined: 18 Jan 2010 Posts: 14

Hi, 0x200 is start address of function that pass string char by char to printf function and 0x20C is start address of string.