Quoting Siegmar Gross :
Hi Oscar,
The warnings of type "cast to pointer from integer of different size"
are provoked when a jlong (64 bit handle in Java) is copied to a C
pointer (32 bit) or vice versa.
These warnings could be avoided with methods like these:
void* ompi_java_cHandle(jlo
Hi Oscar,
> The warnings of type "cast to pointer from integer of different size"
> are provoked when a jlong (64 bit handle in Java) is copied to a C
> pointer (32 bit) or vice versa.
>
> These warnings could be avoided with methods like these:
>
> void* ompi_java_cHandle(jlong handle)
Hi,
I have one more problem with process bindings (both machines use
Solaris 10 with Sparc processors).
tyr hello_1 149 which mpicc
/usr/local/openmpi-1.7.4_64_cc/bin/mpicc
tyr hello_1 150 mpicc environ_mpi.c
tyr hello_1 151 mpiexec -np 2 --host rs1 a.out
tyr hello_1 152
Do you have any ideas
Hi Ralph,
thank you very much for your reply. I have changed my rankfile.
rank 0=rs0 slot=0:0-1
rank 1=rs0 slot=1
rank 2=rs1 slot=0
rank 3=rs1 slot=1
Now I get the following output.
rs0 openmpi_1.7.x_or_newer 108 mpiexec --report-bindings \
--use-hwthread-cpus -np 4 -rf rf_rs0_rs1 hostname
--
Hi,
The warnings of type "cast to pointer from integer of different size"
are provoked when a jlong (64 bit handle in Java) is copied to a C
pointer (32 bit) or vice versa.
These warnings could be avoided with methods like these:
void* ompi_java_cHandle(jlong handle)
{
unio
On Feb 7, 2014, at 11:33 PM, Siegmar Gross
wrote:
> Hi,
>
> today I tested rankfiles once more. The good news first: openmpi-1.7.4
> now supports my Sun M4000 server with Sparc VII processors on the
> command line.
>
> rs0 openmpi_1.7.x_or_newer 104 mpiexec --report-bindings -np 4 \
> --bind
