How to tell Cadence to use a 32-bit or 64-bit executable?

[John Gianni]

=================================================
These two questions came up today and I figured others would
learn by posting them here for interested Cadence users to benefit.
=================================================
Q1: How can you tell if your OS supports 64 bit?
A1: SOLARIS: % /bin/isainfo -b
(returns 64 on a 64 bit machine)
(returns 32 on a 32 bit machine)

HPUX: % /bin/getconf KERNEL_BITS
(returns 64 on a 64 bit machine)
(returns 32 on a 32 bit machine)

AIX: # /usr/sbin/bootinfo -y
MUST BE ROOT TO EXECUTE THIS COMMAND!
I don't have an account so I don't know what it
outputs.
Do you?

LINUX: % uname -m
(returns x86_64 on a 64 bit em64t/opteron
machine)
(returns i686 on a 32 bit i686 machine)
(returns i586 on a 32 bit i586 machine)
(returns i486 on a 32 bit i486 machine)
=================================================
Q2: How does DFII (aka Virtuoso) decide which executable to use?
A2: For DFII (aka Virtuoso), it seems to work this way ...

1. When you run the DFII command ...
e.g., csh% layout

2. This runs the "layout" wrapper in your cds_root path ...
e.g., /cds/IC61_sun4v/tools/dfII/bin/layout

3. Which runs the "layout.exe" executable in cds_root ...
e.g., `cds_root layout`/tools/dfII/bin/layout.exe

4. Which has a call to "wrap3264" compiled into it ...
e.g., csh% strings layout.exe | grep wrap3264

5. Which, essentially, runs an API 'similar' to the aforementioned:
SOLARIS: % /bin/isainfo -b
HPUX: % /bin/getconf KERNEL_BITS
AIX: # /usr/sbin/bootinfo -y (must be root)
LINUX: % uname -m

6. Which either reports your OS is "32" or "64" bit enabled.

7. If the OS supports 64 bit but you did not set the shell environment
variable CDS_AUTO_64BIT, then, the wrapper will pick the 32 bit
binary
(by default) even if you have both 64-bit & 32-bit executables
in your dfII/bin/{32bit|64bit} directory.

However, if you only have 64-bit executables, then it will choose
the
64 bit executable.

8. If the user had set the variable "CDS_AUTO_64BIT" then the wrapper
will try to do as told, e.g.: set CDS_AUTO_64BIT
{ALL|NONE|"<list>"}

setenv CDS_AUTO_64BIT ALL
- invokes all applications as 64-bit, where possible.
e.g., `cds_root layout`/tools/dfII/bin/64bit/layout.exe

setenv CDS_AUTO_64BIT NONE
- invokes all applications as 32-bit.
e.g., `cds_root layout`/tools/dfII/bin/32bit/layout.exe

setenv CDS_AUTO_64BIT "<list>"
- invokes only the executables included in the list, if available,
as 64-bit case-sensitive executable names delimited by
comma (,), semi-colon(, or colon).
Example: setenv CDS_AUTO_64BIT "pipo,layout.exe"
=================================================
As always, please improve so all benefit from every action.
=================================================
John Gianni
--
Nothing I state on the USENET is prior reviewed by anyone!

 

[John Gianni]

setenv CDS_AUTO_64BIT ALL
setenv CDS_AUTO_64BIT NONE
setenv CDS_AUTO_64BIT "si pipo layout.exe layoutPlus.exe ERC cdba2icc ivVerify"

In addition, in USENET post:
- http://tinyurl.com/pj7la
The Sourcelink article below is referenced:
- http://sourcelink.cadence.com/docs/db/kdb/2001/June/1842831.html
Which provides additional syntactic examples such as:
- setenv CDS_AUTO_64BIT "EXCLUDE:si"

The EXCLUDE:<executable> syntax tells Cadence to use 64 bit executable
for all available Cadence products except those in the EXCLUDE list.

As always, I hope this example helps others,
John Gianni
Nothing stated here is prior sanctioned by my employer.

Note: http://tinyurl.com/pj7la ==>
http://groups.google.com/group/comp.cad.cadence/browse_thread/thread/2c5a08e8d6212998/f2505b21ed0bcbeb?