environment variable CDS_AUTO_64BIT

C

cad_user

Guest
I've noticed most Cadence tools now use the CDS_AUTO_64BIT
as a convenient "default" setting for launching 64-bit
executables. On our workplace AMD Opteron and Solaris8
machines, I've noticed some quirky behavior.

1) Some applications in SOC42 seem to use ":" separators.
#!/bin/csh
setenv CDS_AUTO_64BIT "wroute:sroute:celtic";

# ^^^ wroute, sroute, celtic launch 64-bit version

2) Other applications in SOC42 use a SPACE

setenv CDS_AUTO_64BIT "pks_shell ac_shell rtle";

# ^^^ pks_shell, ac_shell, rtle launch 64-bit version

3) Now, if you try to combine everything into one line,

setenv CDS_AUTO_64BIT "wroute:sroute:celtic pks_shell ..."

^^^ doesn't work at all. *All* programs launch in 32-bit mode!

How exactly is CDS_AUTO_64BIT supposed to work? I could
have sworn SOC41 used a SPACE-separator for every binary.
But now it looks like some programs require ":" separator
(and get confused if there is a SPACE, anywhere.)

Anyway, for now I use the command-line option "-64". At
least that option works consistently across all Cadence apps.

wroute -64; # force 64-bit (override CDS_AUTO_64BIT!)
pks_shell -64; # force 64-bit (override CDS_AUTO_64BIT!)
 
You tried with colons wroute:sroute:celtic:pks_shell:ac_shell:rtle only ?
Click to expand...
Yes, that only works for wroute, sroute, celtic. The other programs
don't recognize the environment-var CDS_AUTO_64BIT, unless the program
names are separated with SPACES.
 
On Thu, 12 May 2005 04:32:57 GMT, "cad_user" <cad_user@nowhere.net> wrote:

You tried with colons wroute:sroute:celtic:pks_shell:ac_shell:rtle only ?

Yes, that only works for wroute, sroute, celtic. The other programs
don't recognize the environment-var CDS_AUTO_64BIT, unless the program
names are separated with SPACES.
Click to expand...
There is a common wrapper which is used for supporting 64 bit, which many
(but not all) 64 bit tools use. The syntax supported by tools in the IC stream
is the correct one. The program names should be colon, comma, or semicolon
separated, and you can also use the keywords ALL, INCLUDE and EXCLUDE (see the
dfII config docs for more details).

If there's a tool that doesn't support this syntax, please contact customer
support to get this resolved. From a quick search I couldn't find a PCR on
this (I didn't look very thoroughly though).

Andrew.
 
On 15 May 2005 21:38:59 -0700, "Erik Wanta" <erikwanta@starband.net> wrote:

How to run in 64 bit mode should be universal for all wrappers. Should
PCRs be opened for spectre and ultrasim? I think one runs spectre in
64-bit mode with spectre -64. For ultrasim (setenv USIM64 1).

Hello Erik,
I filed doc PCR 711632 to address this documentation issue.
Regarding your inquiry related to Ultrasim, ultrasim64 is supported
for
both solaris and hp platforms, the binary is called ultrasim64. To use
it, you need to set the env variable USIM64 to 1 (as following), and
then run ultrasim by invoking "ultrasim" (not ultrasim64). Assuming
64bit version has been successfully installed, 64bit ultrasim would be
called in batch mode or from ADE.
% setenv USIM64 1

See http://sourcelink.cadence.com/docs/db/kdb/2005/Feb/11022484.html.
---
Erik
Click to expand...
Hi Erik,

spectre supports CDS_AUTO_64BIT. All tools that use the common 32/64 bit
wrapper executable support -64 as well, and spectre is using that.

I just checked, and ultrasim also uses the common wrapper (at least in MMSIM60
onwards) - and so supports CDS_AUTO_64BIT and -64 command line switch. It
no longer supports the USIM64 env var, from my tests.

That solution (which was written by me) does actually say you can use
CDS_AUTO_64BIT or -64.

I'll get solution 11143508 corrected, as this is no longer valid. In fact I
just did some further tests, and USIM64 worked up until USIM42. From
MMSIM60 ultrasim switched to use the standard mechanism.

Regards,

Andrew.
 
You tried with colons wroute:sroute:celtic:pks_shell:ac_shell:rtle only ?

cad_user wrote:
I've noticed most Cadence tools now use the CDS_AUTO_64BIT
as a convenient "default" setting for launching 64-bit
executables. On our workplace AMD Opteron and Solaris8
machines, I've noticed some quirky behavior.

1) Some applications in SOC42 seem to use ":" separators.
#!/bin/csh
setenv CDS_AUTO_64BIT "wroute:sroute:celtic";

# ^^^ wroute, sroute, celtic launch 64-bit version

2) Other applications in SOC42 use a SPACE

setenv CDS_AUTO_64BIT "pks_shell ac_shell rtle";

# ^^^ pks_shell, ac_shell, rtle launch 64-bit version

3) Now, if you try to combine everything into one line,

setenv CDS_AUTO_64BIT "wroute:sroute:celtic pks_shell ..."

^^^ doesn't work at all. *All* programs launch in 32-bit mode!

How exactly is CDS_AUTO_64BIT supposed to work? I could
have sworn SOC41 used a SPACE-separator for every binary.
But now it looks like some programs require ":" separator
(and get confused if there is a SPACE, anywhere.)

Anyway, for now I use the command-line option "-64". At
least that option works consistently across all Cadence apps.

wroute -64; # force 64-bit (override CDS_AUTO_64BIT!)
pks_shell -64; # force 64-bit (override CDS_AUTO_64BIT!)
Click to expand...
 
How to run in 64 bit mode should be universal for all wrappers. Should
PCRs be opened for spectre and ultrasim? I think one runs spectre in
64-bit mode with spectre -64. For ultrasim (setenv USIM64 1).

Hello Erik,
I filed doc PCR 711632 to address this documentation issue.
Regarding your inquiry related to Ultrasim, ultrasim64 is supported
for
both solaris and hp platforms, the binary is called ultrasim64. To use
it, you need to set the env variable USIM64 to 1 (as following), and
then run ultrasim by invoking "ultrasim" (not ultrasim64). Assuming
64bit version has been successfully installed, 64bit ultrasim would be
called in batch mode or from ADE.
% setenv USIM64 1
Click to expand...
See http://sourcelink.cadence.com/docs/db/kdb/2005/Feb/11022484.html.
---
Erik
 
You must log in or register to reply here.

Welcome to EDABoard.com

Sponsor

Back
Top