Github messages for voidlinux
 help / color / mirror / Atom feed
* [ISSUE] intel-gmmlib package requires more CPU features than Void baselineand is compiled with -march=corei7
@ 2021-03-28  6:09 ericonr
  2021-04-06  2:15 ` tornaria
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: ericonr @ 2021-03-28  6:09 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 897 bytes --]

New issue by ericonr on void-packages repository

https://github.com/void-linux/void-packages/issues/29801

Description:
Reported by @sgn on IRC.

Per https://github.com/intel/gmmlib/blob/2072b0d1e8ba2cba2f94bc2c1fda89d6e457a50b/Source/GmmLib/Linux.cmake :

```
    # General optimization options
    -march=${GMMLIB_MARCH}
    -mpopcnt
    -msse
    -msse2
    -msse3
    -mssse3
    -msse4
    -msse4.1
    -msse4.2
    -mfpmath=sse
    -finline-functions
    -fno-short-enums
    -Wa,--noexecstack
    -fno-strict-aliasing
    # Common defines
    -DUSE_MMX
    -DUSE_SSE
    -DUSE_SSE2
    -DUSE_SSE3
    -DUSE_SSSE3
```

`GMMLIB_MARCH` is set to `corei7` by default, but we can fix that with `configure_args`. What I also worry about are all the `-msse*` switches, since afaik they can affect generated code that isn't directly using compiler intrinsics for them.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: intel-gmmlib package requires more CPU features than Void baselineand is compiled with -march=corei7
  2021-03-28  6:09 [ISSUE] intel-gmmlib package requires more CPU features than Void baselineand is compiled with -march=corei7 ericonr
@ 2021-04-06  2:15 ` tornaria
  2021-04-06  3:28 ` ericonr
  2021-04-11  2:57 ` [ISSUE] [CLOSED] " ericonr
  2 siblings, 0 replies; 4+ messages in thread
From: tornaria @ 2021-04-06  2:15 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 299 bytes --]

New comment by tornaria on void-packages repository

https://github.com/void-linux/void-packages/issues/29801#issuecomment-813772679

Comment:
It seems, according to https://github.com/intel/gmmlib#supported-platforms, that the supported graphic devices already imply the cpu supports all that.



^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: intel-gmmlib package requires more CPU features than Void baselineand is compiled with -march=corei7
  2021-03-28  6:09 [ISSUE] intel-gmmlib package requires more CPU features than Void baselineand is compiled with -march=corei7 ericonr
  2021-04-06  2:15 ` tornaria
@ 2021-04-06  3:28 ` ericonr
  2021-04-11  2:57 ` [ISSUE] [CLOSED] " ericonr
  2 siblings, 0 replies; 4+ messages in thread
From: ericonr @ 2021-04-06  3:28 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 520 bytes --]

New comment by ericonr on void-packages repository

https://github.com/void-linux/void-packages/issues/29801#issuecomment-813795353

Comment:
It seems `corei7` is mostly equivalent to nehalem:

```
  {"corei7", PROCESSOR_NEHALEM, CPU_NEHALEM, PTA_NEHALEM},
```

I don't know if it makes sense to force a different target, then - `corei7` probably generates slightly better code here than `x86_64` would. Maybe we it might just be enough to document these constraints in the template itself. Thanks for the hint!


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [ISSUE] [CLOSED] intel-gmmlib package requires more CPU features than Void baselineand is compiled with -march=corei7
  2021-03-28  6:09 [ISSUE] intel-gmmlib package requires more CPU features than Void baselineand is compiled with -march=corei7 ericonr
  2021-04-06  2:15 ` tornaria
  2021-04-06  3:28 ` ericonr
@ 2021-04-11  2:57 ` ericonr
  2 siblings, 0 replies; 4+ messages in thread
From: ericonr @ 2021-04-11  2:57 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 900 bytes --]

Closed issue by ericonr on void-packages repository

https://github.com/void-linux/void-packages/issues/29801

Description:
Reported by @sgn on IRC.

Per https://github.com/intel/gmmlib/blob/2072b0d1e8ba2cba2f94bc2c1fda89d6e457a50b/Source/GmmLib/Linux.cmake :

```
    # General optimization options
    -march=${GMMLIB_MARCH}
    -mpopcnt
    -msse
    -msse2
    -msse3
    -mssse3
    -msse4
    -msse4.1
    -msse4.2
    -mfpmath=sse
    -finline-functions
    -fno-short-enums
    -Wa,--noexecstack
    -fno-strict-aliasing
    # Common defines
    -DUSE_MMX
    -DUSE_SSE
    -DUSE_SSE2
    -DUSE_SSE3
    -DUSE_SSSE3
```

`GMMLIB_MARCH` is set to `corei7` by default, but we can fix that with `configure_args`. What I also worry about are all the `-msse*` switches, since afaik they can affect generated code that isn't directly using compiler intrinsics for them.

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2021-04-11  2:57 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-03-28  6:09 [ISSUE] intel-gmmlib package requires more CPU features than Void baselineand is compiled with -march=corei7 ericonr
2021-04-06  2:15 ` tornaria
2021-04-06  3:28 ` ericonr
2021-04-11  2:57 ` [ISSUE] [CLOSED] " ericonr

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).