Whats going on @ CCS ?

[StarFire54]

Some month ago, CCS announces compiler version 4.1 with some highlights like string concatenation with a "+" and so on...
This announcement is now erased from the CCS pages....
But now for about 2 month, the compiler revision sticks to 4.099
and about a dozen faults and errors are still in 4.099
(memory read errors, erroneous watches, different and erroneous display of watch and "hover over variable" display and much more...)

I renewed my compiler subscriptions now two month before and got nothing but two month lost of my renewal time....

Whats going on?
A bad info is definitively better than **NO** info....

Helmut

[FvM]

There have been various discussions regarding delay of V4.1 in the forum.

[Guest]

4.100 is out today but it doesn't seem to be the big update it was supposed to be.
Certainly doesn't seem to be worth renewing our license.

[Piccolo]

"What's going on at CCS? Who ever can know"
I've had a circuit built for months waiting for CCS to provide a compiler that works with the PIC16F1937, and today, with version 4.100, I was able to get the LCD driver working! I, for one, remain of the mind that even with all of the faults, it's still a good value.

[n-squared]

I am just about to give up.
Almost all of my projects which compiled and ran under V4.099 just fine, crash V4.100. It gives me "internal error 0. Please contact CCS".

How is this possible?
Also they changed the header files once again and deleted definitions.
One example is the VSS_VDD is now missing from 18F87J11.h.

I have waited almost three months for a new release. I was told by CCS tech support that bugs I found would be taken care of in 4.100.

If I didn't have so much invested in code for CCS, I think this would be the time to make a change.

For now, I will stay with V4.099.


_________________
Every solution has a problem.

[FvM]

Some collateral damage could be expected with change to V4.100.

I was rather surprized, that my PIC24 application continued operation (it had to be adapted before to compensate
bugs respectively "changes" in V4.094 and V4.099). I had expected new issues with V4.100.

I only found one with a PCM application, where one instance of a preprocessor directive

[StarFire54]

Version 4.100 is out and the hassle begins again......
All my Projects up to 4.099 compiled without problems
stops compiling with 4.100 with the message, that an internal Error occurred, and should contact CCS... ;-((
Also, the compiler gives warnings where 4.099 does not, 4.100 structurized variables different as in 4.099 and so on.
And that all WITHOUT ANY WARNING OR NOTIFYING FROM CCS!!!)
My current project has up to now 15.300 lines of code, what trouble i have
with such unnotified differences, no one can imagine that!

Up to now i registered CCS Compilers PCW/PCWH for three years, but
it was not worth the value!
I am not really sure if i realize the next big project with this unstable, inconsistent compiler!

The only thing which is really consistent is, that old and dumb errors are not resolved. Instead every new version holds more and new errors.
What a "good" support!

Helmut
(very angry to debug 15.300 lines of code again .....)

[dyeatman]

So far I have recompiled most of my large projects. The largest in my case is about 7,000 lines. All the programs all had minor compile issues that caused errors. One where I had a variable declared short but assigned a value of 5 later in the program. Version 4.100 caught it where none of the other versions did.

The only program where I encountered a serious compile issue (a crash similar to yours) was one that used pointers to ROM for an LCD display. (I assume you have seen the readme.txt file?) I corrected the pointer syntax to confirm to the readme file and everything was good from there on.

To find the cause of the crash (I suspected it was pointer issues) I commented out lines of code until the crashes stopped. It turned out to be bad syntax in a pointer declaration.

I did get a lot more warnings than I had previously but the #ignore_warnings line took care of that.

FWIW...
_________________
Google and Forum Search are some of your best tools!!!!

[StarFire54]

Hi dyeatman,

Thanks for your response but I am sure that this error has nothing
to do with rom pointers.
The error message is: "Error #44 at line 356, internal error in file "xxxx.c" , call CCS.
The file in error is the file containing main() and the line in error is
behind main() closing brace and 2 line numbers behind (!) the source files end......
V4.99 compiles without errors, a check with a Hex-Editor shows no file anomalies ;-((

How should I comment this out?? ;-)

btw. I got some weeks ago a memory control dll from CCS support wich corrects some problems in communication with ICD-U64. I installed this and it works better (not perfect, but better) than the .dll coming with 4.099.
In V 4.100 I think that the "old" memory control dll is included, because I have memory reads errors with U64 as usual...

[Guest]

4.101 is out now.

[portscanner]