Skip to content

Conversation

@henryiii
Copy link
Collaborator

@henryiii henryiii commented Oct 12, 2020

Drops an old workaround for #94, and adds a workaround developed for PGI in #2479.

I've tried to build 2.5.0, 2.4.0, 2.3.0, 2.2.0, and 2.0.0 on Intel 17, and none of them can build the py::vectorize code in the tests. Intel 18 seems to be the first one that can. So I think we should simply say we support Intel 18+, and drop the list of older versions that support Intel 16 and 15, since the support wasn’t even complete and these versions are quite old now anyway.

  • fix: Intel 18+ fully supported
  • fix: Intel compiler workaround no longer needed

Also gathering a bit of readme cleanup I'd been collecting.

Tested on 18.0 and 19.1.

@henryiii henryiii added this to the v2.6.0 milestone Oct 12, 2020
Copy link
Collaborator

@YannickJadoul YannickJadoul left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So this is you testing locally, then? @ax3l is still working on the CI part of this in #2573?

@henryiii
Copy link
Collaborator Author

Yes. We can't test anything before 20.2 in CI AFAIK due to Intel licensing.

@YannickJadoul
Copy link
Collaborator

Yes. We can't test anything before 20.2 in CI AFAIK due to Intel licensing.

Booooooooo! Well, not our problem, then, if Intel won't help us support their compiler...

@wjakob
Copy link
Member

wjakob commented Oct 12, 2020

LGTM!

@henryiii
Copy link
Collaborator Author

henryiii commented Oct 12, 2020

Sadly this doesn't solve the instant segfault for 20.2, though, seen in #2573

@henryiii henryiii merged commit 993495c into pybind:master Oct 12, 2020
@henryiii henryiii deleted the fix/intel branch October 12, 2020 20:31
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

Successfully merging this pull request may close these issues.

3 participants