Stats

  • Locked Locked
  • Replies 6
  • Subscribers 92
  • Views 14510
  • 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

TCL

Brian Harrison

Hello,

Is there a proper way to load a dynamically loadable TCL extension in encounter?

example:  www.swig.org/tutorial.html

When I complile the above example and try to load it within encounter I get:

couldn't load file "./example.so": ./example.so: cannot open shared object file: No such file or directory

This works fine within a normal tcl shell.

On a previous project I wrote crude placement algorithm in TCL using encounter commands.  This was done to overcome limitations with encounter clock tree synthesis with IBM ASIC methodology.   The algorithm worked great, but was slow since being in TCL.   I could speed this up in C/C++ using SWIG to create the TCL wrapper.  

Any help?

Best Regards,

Brian

 

Parents

  • I summoned help from our TCL blackbelts internally and I *think* I stumbled onto the same problem as you.  I built example.so on 32-bit and then ran on 64-bit Encounter and got this error message:

    UNIX> encounter
    encounter 1> load example.so
    couldn't load file "example.so": example.so: cannot open shared object file: No such file or directory

    In my case, I have Encounter automatically run in 64-bit mode when I'm on a 64-bit machine with this env var (consequently I don't think about whether I'm running 32-bit or 64-bit):

    setenv CDS_AUTO_64BIT ALL

    If I force 32-bit:

    UNIX> encounter -32
    encounter 1> getBuildArch
    32bit
    encounter 2> load example.so
    ->Works no problem

    Looks like the key is to make sure you're running Encounter on the same platform and architecture as you compiled.

    When you chance to have a look, please let us know whether this resolved your issue.  If it does not, we have the right people lined up to help out.

    Thanks!
    Bob

Reply

  • I summoned help from our TCL blackbelts internally and I *think* I stumbled onto the same problem as you.  I built example.so on 32-bit and then ran on 64-bit Encounter and got this error message:

    UNIX> encounter
    encounter 1> load example.so
    couldn't load file "example.so": example.so: cannot open shared object file: No such file or directory

    In my case, I have Encounter automatically run in 64-bit mode when I'm on a 64-bit machine with this env var (consequently I don't think about whether I'm running 32-bit or 64-bit):

    setenv CDS_AUTO_64BIT ALL

    If I force 32-bit:

    UNIX> encounter -32
    encounter 1> getBuildArch
    32bit
    encounter 2> load example.so
    ->Works no problem

    Looks like the key is to make sure you're running Encounter on the same platform and architecture as you compiled.

    When you chance to have a look, please let us know whether this resolved your issue.  If it does not, we have the right people lined up to help out.

    Thanks!
    Bob

Children
No Data

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.