Stats

  • Locked Locked
  • Replies 4
  • Subscribers 125
  • Views 2159
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

what is the difference between "parseAsCEL no" and "parseAsCEL don't use"?

zssfred

subject says it all.

Parents
  • Andrew Beckett

    There is no difference. If you say "don't use" it doesn't explicitly set parseAsCEL and so it would be the default (which is "no"). If you set it to "no", it does the same thing.

    It's a bit confusing, I agree...

    Andrew.

Reply
  • Andrew Beckett

    There is no difference. If you say "don't use" it doesn't explicitly set parseAsCEL and so it would be the default (which is "no"). If you set it to "no", it does the same thing.

    It's a bit confusing, I agree...

    Andrew.

Children
  • zssfred
    in reply to Andrew Beckett

    It is little bit weird. Before I posted here, if I single-quoted the value like 'value', and if I selected "don't use", the auCdl netlist will keep the quote and I selected "no", the auCdl netlist will strip the quote.

    But after I read the post, the quote is always there no matter "don't use" or "no". Yes, they have no difference now. The interesting thing is the pPar() is always parsed even in "no" mode. Say, we have defined parameter like a=pPar(b)+pPar(c), the netlist is always like a=b+c.

    Thanks.

    Fred

  • Andrew Beckett
    in reply to zssfred

    That's partly because pPar() is not entirely "CEL" but this is slightly surprising. It might depend upon the netlister (auCdl may be different from spectre, for historical reasons for example). It may also depend on the parseAsNum setting.

    I suggest you contact customer support if you need this exploring in more detail (I don't have the bandwidth at the moment to research and find out the answer, sorry).

    Regards,

    Andrew.

  • zssfred
    in reply to Andrew Beckett

    Sure. Already, opened case.

    Thanks.

    Fred

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.