-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Intel compiler discussion issue #2771
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
Comments
In C++17 the noexcept specification is part of the type. That does not mean the error makes any more sense. |
Just converted a project i work on with pybind11 to intels DPC++ 2022 and C++ 2022 compiler and it compiles but python hates it, throws a DLL not found error. If anyone has any updates on issues with intels OneAPI compilers please do reply. |
What DLL? What OS? Could you paste the error? We shouldn't be requiring a DLL, this is a header only no dependency project... |
It gave a DLL load failed when importing the module. ImportError: DLL load failed while importing GavinBackendDatasetUtils: The specified module could not be found. Im on windows 10. |
I have a feeling it has something to do with https://docs.python.org/3/library/os.html#os.add_dll_directory (new in Python 3.8) - for security reasons, Python has to be told where modules live. If you are not doing a "normal" install into site-packages, it won't work unless you also fiddle with that |
Hey, I also have the same problem. I wrote a simple example project to be compiled with
Is there a way to get more debug information about this? @henryiii could you explain a bit more what you mean with the On linux side it work :) |
I could trace down the problem a bit more. I seems that error comes from a missing
which gave this output:
When I then manually copy Any ideas to automate this? I am now also blocked again when I really want to use |
any news on this? |
for me, not even compilation works, fails with the following error:
Icx version:
|
Intel support is just about the only thing holding up version 2.6.2; there are now three open PRs on it. I've been working with Intel's support team, and they would like standalone examples of the bugs if possible. This helps track the progress, and is a call for standalone examples of the bugs.
PR 1: #2573: Initial support for “OneAPI” Intel compilers, using CI for the first time. (We’ve always supported older compilers, like 18 & 19, but had no CI and only tested C++11 - C++14 was actually C++11 due to a typo)
Constructor() = default
is broken, we have to useConstructor {}
instead in several places. Also~Destructor() = default
, too.PR 2: #2729: Builds / reimplements PR 1, from someone else, but also address new C++17 issues since we have never tested with C++17 on earlier compilers (14 either, actually, due to a typo):
enable_if_t<!all_of<is_positional<Args>...>::value>
- have to use workaround to define in multiple parts#if defined(__cpp_fold_expressions) && !defined(__INTEL_COMPILER)
Intel compiler produces an internal error on this fold expression (This was broken on ICC 19 too)<aligned_new>
to get ICC to follow the standard, but that seems to be a known compatibly issuePR 3: #2769 Just opened yesterday to try icpx. The CI configs may have an issue there, it’s not running at all yet.
@ax3l @mkuron @tobiasleibner @YannickJadoul @bstaletic might be interested.
I'm thinking about adding a workaround def so that we can disable the workarounds at will, to see if they are still needed. That might be the best way forward for us without interfering with getting the problems fixed upstream.
The text was updated successfully, but these errors were encountered: