-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Restore C++17 mode for Interpreter/Cling #623
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
Conversation
This was lost while migrating to newer LLVM/Clang stack. Signed-off-by: David Abdurachmanov <[email protected]>
|
Starting build on |
|
Build failed on ubuntu14/native. |
|
Build failed on centos7/gcc49. Failing tests: |
|
Build failed on slc6/gcc62. Failing tests: |
|
Build failed on slc6/gcc49. Failing tests: |
|
It seems this didn't end up in our llvm.git as it probably won't now and next time it would be wiped away again. I will submit it for upstreaming... |
|
Here are more details on where segfault happens:
|
|
It seems that Could we have a reduced example of the code that's being passed and mishandled by |
|
Ah, yeah, I didn't check upper frames. Probably |
|
As you said the |
|
@pcanal needs to have a look here... |
|
Here is JIRA ticket for segfault: https://sft.its.cern.ch/jira/browse/ROOT-8825 |
This was lost while migrating to newer LLVM/Clang stack.
Otherwise
-std=c++11is added to compilation lines overriding-std=c++1z. Thus Cling/Interpreter ends up in C++11 mode and then we get errors aboutstd::string_viewonly being available in C++17.Compiled on Fedora 26 with
-Dminimal=ON -Dcxx17=ON. Note, it still fails to build near the end:Signed-off-by: David Abdurachmanov [email protected]