Search found 19 matches

I received a new math.h file from CCS that should correct the problem. Only one thing: they added two casts to int8 but it should have been int8*. Didn't they test their own corrections ? I had the tw ...

The LOG problem, sorry.
thomasj

One last message - I reported the float problem to CCS and they sent me a new math.h - but it is still wrong ! Using the corrections I got from this forum works fine though. CCS used a cast of (int8), ...

Hi again,

Ok i see your point, but I'd still rather have a compiler that generated a too big a program rather than a 'faulty' one. One thing: I don't see what you mean by first saying

"The ...

But your post of Nov 18, 2004 only talks about multiplying 8 bit integers and then expecting 16 bits as a result, i.e. promoting one or both of the operands to the same type as the _result_ - this wor ...

Hi, yes it works after the proposed changes, thanks.

Haven't CCS heard of regression testing - if you change ANYTHING you have to test EVERYTHING ? In this particular case it is even simpler - have ...

Hi,

Ok, thanks for all the help. I guess I have to live with this quirk, but I must say that it is becoming a bit tricky to remember all the little exceptions :-) In the last two monts or so I have ...

Ok, i didn't see those topics. Regarding Ttelmah's post at the end: My problem is not of the type small type * small type => bigger type, but a multiplication of an int16 with a float, and the com ...

Hi again,

This time I have a problem with the automatic type conversion that should work in C. I tried the following short program fragment (excluded init of RS232 etc) :

signed int16 testVal ...

Hi, I have a problem with version 4.023 that doesn't exist in version 3.245. Basically the log function gives the wrong answer. In an otherwise unchanged program these are some results for the two ver ...

Thanks for the help on this, I wanted to be sure my brain wasn't on the fritz. This is actually the second 'compiler malfunction' I found this week, and I started to have some doubts ... :-)

The PI ...

dyeatman - Yes, I know that a value different from 0 is regarded as a TRUE value, but my point is that the compiler help (and the manual) states that the return value should be either zero or one, and ...

Hi, I use an input function call to read a digital pin and assign the result to a 16 bit int. When the pin is high sometimes I get a value different from 1; see the following small code snippet:

...

Ok, thanks for the help with debugging this! I can work around it in my code, the ram struct is static so I can use it directly instead of going trough a pointer (the copy was in a subroutine, hence t ...

Try this change. It uses a pointer to the struct in ram, and fails as long as
the keyword const is in place, but works otherwise. My printout looks like this:

Before: 0 0 0 .
After: 0 22 3 ..... ...