Interesting. Thanks for the tip about the SSE instruction.
In fact one machine has flags of:
--
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt
rdtscp lm 3dnowext 3dnow constant_tsc no
Hello,
Josh Hursey, le Thu 09 Jun 2011 17:03:29 +0200, a écrit :
> Program terminated with signal 4, Illegal instruction.
> #0 0x0041d8d9 in hwloc_weight_long ()
> 0x0041d8d9 : popcnt
> 0xfff8(%rbp),%rax
This is SSE4 indeed. You could check in grep sse4 /proc/c
Below is some disassembly generated from gdb from the core file that
was generated. The signal is an illegal instruction, not a segv as I
mentioned previously (sorry about that). I also included some
information about the lstopo file and configure parameters below.
Thanks,
Josh
--
Josh Hursey, le Thu 09 Jun 2011 14:52:39 +0200, a écrit :
> The odd thing about this environment is that the head node seems to
> have a slightly different setup than the compute nodes (not sure why
> exactly, but that's what it is). So hwloc is configured and runs
> correctly on the head node, but
The odd thing about this environment is that the head node seems to
have a slightly different setup than the compute nodes (not sure why
exactly, but that's what it is). So hwloc is configured and runs
correctly on the head node, but when it is asked to run on the compute
nodes it segvs at the call
Josh Hursey, le Wed 08 Jun 2011 22:28:53 +0200, a écrit :
> I hit a problem when installing hwloc statically on a machine with a
> slightly different gcc support libraries and OSs on the head/compile
> node versus the compute nodes. The builtin functions would cause hwloc
> to segfault when run on
On Jun 8, 2011, at 5:30 PM, Dave Goodell wrote:
>> Is there a reason we wouldn't disable it in OMPI's hwloc by default?
>
> Performance will be better when left enabled on platforms where the compiler
> and the architecture are in agreement...
I'm not too concerned about hwloc's performance in
On Jun 8, 2011, at 4:21 PM CDT, Jeff Squyres wrote:
> Is there a reason we wouldn't disable it in OMPI's hwloc by default?
Performance will be better when left enabled on platforms where the compiler
and the architecture are in agreement...
IMO Josh's use case is a bit exotic. He's using one s
Is there a reason we wouldn't disable it in OMPI's hwloc by default?
On Jun 8, 2011, at 5:14 PM, Josh Hursey wrote:
> In short, I haven't yet. I figured out the problem was in hwloc, and
> started with the hwloc branch by itself.
>
> In Open MPI, we should be able to pass the --disable-gcc-built
In short, I haven't yet. I figured out the problem was in hwloc, and
started with the hwloc branch by itself.
In Open MPI, we should be able to pass the --disable-gcc-builtin from
the main configure, right (since we pull in config/hwloc_internal.m4)?
So we would pass it similar to how we had to pa
Josh --
How did you get this disabled from within OMPI? We don't invoke hwloc's
configure via sub-shell; we directly invoke its m4, so we don't have an
opportunity to pass --disable-gcc-builtin. Unless you passed that to the
top-level OMPI configure script...?
On Jun 8, 2011, at 4:28 PM, Jo
(This should have gone to the devel list)
The attached patch adds a configure option (--disable-gcc-builtin) to
disable the use of GCC __builtin_ operations, even if the GCC compiler
supports them. The patch is a diff from the r3509 revision of the
hwloc trunk.
I hit a problem when installing hwl
12 matches
Mail list logo
