Pumpkin, Inc.

Pumpkin User Forums

Can't generate code for expression...compiler response

If you think you've found a bug or other mistake in your Salvo distribution, post it here.

Can't generate code for expression...compiler response

Postby din » Mon Nov 10, 2003 4:02 am

Hi,

In the file msg.c, the expression

code:

OSMsg("OSWaitMsg",
OSMakeStr("task %d acquired message %d (now %d).", OStID(OScTcbP), OSeID(ecbP), ecbP->event.msgP));

returns an error with my ht-pic v8.01 compiler.

quote:
Can't generate code for expression...

The expression may be simplified.

din
 
Posts: 7
Joined: Sat Oct 18, 2003 11:00 pm

Re: Can't generate code for expression...compiler response

Postby aek » Mon Nov 10, 2003 5:21 am

Again, need more info.

The various problems you're having seem to suggest a more serious problem -- with a current Salvo release and an up-to-date version of PICC, you shouldn't be having these problems.

Plus, all of the code you've listed is "active" in the various Salvo Pro tutorial builds, which build fine (e.g. salvo ut u6sysa u6pro.mcp, which has to build msg.c).

------------------

-------
aek
aek
 
Posts: 1888
Joined: Sat Aug 26, 2000 11:00 pm

Re: Can't generate code for expression...compiler response

Postby din » Mon Nov 17, 2003 5:30 am

Here are details:
I am using the release 3.2.3 for PIC MCU's that is available via ftp.

My compiler: ht-pic 8.01 PL1.

OSLOGGING is set to TRUE.

This can be a compiler limitation. The user manual tells that I may simplify the expression and/or pass through a temporary variable.

To be totally honest, I wrote my own OSMakeStr function cause the standard io library - supplied with the compiler - does not know the function called 'vsprintf'.

din
 
Posts: 7
Joined: Sat Oct 18, 2003 11:00 pm

Re: Can't generate code for expression...compiler response

Postby aek » Mon Nov 17, 2003 12:03 pm

I suspect one of the major reasons why you're seeing this sort of problem is that most of the logging features in Salvo are expected to be used when Salvo is running on an x86, and not the intended embedded target.

For example, we develop in CodeWarrior x86, which has far fewer limitations on complex expressions, etc. than do the embedded compilers we suppprt.

------------------

-------
aek
aek
 
Posts: 1888
Joined: Sat Aug 26, 2000 11:00 pm


Return to Bug Reports

Who is online

Users browsing this forum: No registered users and 0 guests

cron