#67 preprocessor directive not recognized

[Anonymous]

error message:

306: unmatched character () ERROR! syntax error, unexpected K_assign, expecting '(', file: ./bistRtl//EMT_p1500_mbManager_mbCtlr1_mbCtlr.v, line: 307 ERROR! Invalid module item. Did you forget an initial or always?, file: ./bistRtl//EMT_p1500_mbManager_mbCtlr1_mbCtlr.v, line: 307 308: unmatched character ()
ERROR! Invalid module item. Did you forget an initial
or always?, file:
./bistRtl//EMT_p1500_mbManager_mbCtlr1_mbCtlr.v, line: 309
310: unmatched character () ERROR! Invalid module item. Did you forget an initial or always?, file: ./bistRtl//EMT_p1500_mbManager_mbCtlr1_mbCtlr.v, line: 313 336: unmatched character ()

offending lines of code:

ifdef REDUCED_ADDRESS assign maxBnkAddress = (freezeBlockAddr) ? {blockAddrValue,4'd3} : 7'd3;else
assign maxBnkAddress = (freezeBlockAddr) ?
{blockAddrValue,4'd31}: 7'd127;
`endif

[Nobody/Anonymous]

Logged In: NO

BTW...this is for version covered-20060218

[Trevor Williams]

Logged In: YES
user_id=512771

I attempted to place the above lines of code in a file and
compile it with Covered without error. Does this piece of
code compile with other tools? If so, would it be possible
to get the entire file that is causing the problem so that I
can attempt some more debug? Also, are you defining
REDUCED_ADDRESS in a Verilog file or are you defining it on
the command-line? Any help to debug this problem that you
can provide would be greatly appreciated.

Regards,
Trevor Williams

[Trevor Williams]

Logged In: YES
user_id=512771

I did find that Covered did not support multi-line
definitions, so perhaps this is the real issue. It is
difficult to tell with the given description. Could the
owner of this bug please either provide me a small
testcase that replicates the problem or confirm that you
are using a multi-line define (one using the '\' character
at the end of a line)? If nothing is done with this bug
by its sender, I will just close it out in a few weeks.

[SourceForge Robot]

Logged In: YES
user_id=1312539

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).