dtrace discuss - Dec 2008 - dtrace (1M) manpage/ docs seem incorrect re 32/64 bit

The dtrace(1M) manpage seems to be incorrect, it states:

   -32 | -64

         The D compiler produces programs using the  native  data
         model  of  the  operating system kernel. You can use the
         isainfo -b command to determine  the  current  operating
         system  data  model.   If  the  -32 option is specified,
         dtrace forces the D compiler  to  compile  a  D  program
         using the 32-bit data model. If the -64 option is speci-
         fied, dtrace forces the D compiler to compile a  D  pro-
         gram using the 64-bit data model. These options are typ-
         ically not required as dtrace selects  the  native  data
         model  as  the default. The data model affects the sizes
         of integer types and other language properties.  D  pro-
         grams  compiled for either data model can be executed on
         both 32-bit and 64-bit kernels. The -32 and -64  options
         also determine the ELF file format (ELF32 or ELF64) pro-
         duced by the -G option.

If I read this correctly then trying doing "dtrace -G -o foo ..." will
default to being 32-bit on a 32-bit system and 64-bit on a 64-bit system. That
does not seem to be the case however - it always seems to do a 32-bit build if
-64 is not specified.

Further, on systems where bug 6456626 has been fixed, -G will try to guess
whether to do 32-bit or 64-bit compile and so the docs need to be updated to
reflect this as well.

Cheers,
David Holmes
-- 
This message posted from opensolaris.org

Correct. Please file a bug.

Adam

On Wed, Dec 10, 2008 at 09:56:34PM -0800, David Holmes
wrote:
> The dtrace(1M) manpage seems to be incorrect, it states:
> 
>    -32 | -64
> 
>          The D compiler produces programs using the  native  data
>          model  of  the  operating system kernel. You can use the
>          isainfo -b command to determine  the  current  operating
>          system  data  model.   If  the  -32 option is specified,
>          dtrace forces the D compiler  to  compile  a  D  program
>          using the 32-bit data model. If the -64 option is speci-
>          fied, dtrace forces the D compiler to compile a  D  pro-
>          gram using the 64-bit data model. These options are typ-
>          ically not required as dtrace selects  the  native  data
>          model  as  the default. The data model affects the sizes
>          of integer types and other language properties.  D  pro-
>          grams  compiled for either data model can be executed on
>          both 32-bit and 64-bit kernels. The -32 and -64  options
>          also determine the ELF file format (ELF32 or ELF64) pro-
>          duced by the -G option.
> 
> If I read this correctly then trying doing "dtrace -G -o foo ..."
will default to being 32-bit on a 32-bit system and 64-bit on a 64-bit system.
That does not seem to be the case however - it always seems to do a 32-bit build
if -64 is not specified.
> 
> Further, on systems where bug 6456626 has been fixed, -G will try to guess
whether to do 32-bit or 64-bit compile and so the docs need to be updated to
reflect this as well.
> 
> Cheers,
> David Holmes
> -- 
> This message posted from opensolaris.org
> _______________________________________________
> dtrace-discuss mailing list
> dtrace-discuss at opensolaris.org
-- 
Adam Leventhal, Fishworks                     http://blogs.sun.com/ahl