Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Illegal instruction (core dumped) on importing grape #27

Closed
caufieldjh opened this issue Nov 8, 2022 · 4 comments
Closed

Illegal instruction (core dumped) on importing grape #27

caufieldjh opened this issue Nov 8, 2022 · 4 comments

Comments

@caufieldjh
Copy link
Contributor

In another issue that may have something to do with our aging build server:
When we import grape in this environment (see info below), we get only Illegal instruction (core dumped).

cpuinfo output:

processor       : 23
vendor_id       : GenuineIntel
cpu family      : 6
model           : 44
model name      : Intel(R) Xeon(R) CPU           X5675  @ 3.07GHz
stepping        : 2
microcode       : 0x1f
cpu MHz         : 1599.987
cache size      : 12288 KB
physical id     : 1
siblings        : 12
core id         : 10
cpu cores       : 6
apicid          : 53
initial apicid  : 53
fpu             : yes
fpu_exception   : yes
cpuid level     : 11
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 popcnt lahf_lm epb pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid dtherm ida arat flush_l1d
bugs            : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit
bogomips        : 6133.21
clflush size    : 64
cache_alignment : 64
address sizes   : 40 bits physical, 48 bits virtual
power management:
@zommiommy
Copy link
Collaborator

That processor should have a Westmere microarchitecture, which is 2 generations before Haswell, so I suppose that the error is either in the detection of the CPU features or in the compatibility version we ship.

I'm looking into this

@zommiommy
Copy link
Collaborator

Found it! It was a stupid typo on the check.
https://github.com/AnacletoLAB/ensmallen/blob/2cbccc224e2e366c6ab8a897be93ef808accaa72/bindings/python/ensmallen/__init__.py#L14

Here I forgot to put the HASWELL_FLAGS in the set check.

I'm compiling the fixed version, it will be uploaded soon.

@caufieldjh
Copy link
Contributor Author

Aha! Thanks!

@LucaCappelletti94
Copy link
Member

It should be fixed in the new version of ensmallen, do run a pip install -U grape

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants