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

Dynamic linked Terra breaks tests in LLVM 9-11 #477

Closed
elliottslaughter opened this issue Jan 21, 2021 · 5 comments · Fixed by #534
Closed

Dynamic linked Terra breaks tests in LLVM 9-11 #477

elliottslaughter opened this issue Jan 21, 2021 · 5 comments · Fixed by #534

Comments

@elliottslaughter
Copy link
Member

Documenting this so I can move on with the LLVM 10/11 merge.

Errors look like (for example):

513/536 Test #514: unm.t ............................Subprocess aborted***Exception:   0.14 sec
: CommandLine Error: Option 'vector-library' registered more than once!
LLVM ERROR: inconsistency in registered CommandLine options
elliottslaughter added a commit that referenced this issue Jan 23, 2021
As of this merge there are the following known issues with the LLVM 10 and 11 support:

  * #476 cannot include immintrin.h
  * #477 test failures in LLVM 11 when dynamically linked
  * #479 tests fail on macOS with LLVM >= 10
@elliottslaughter
Copy link
Member Author

I'm starting to think this is related not to the LLVM version but something about how LLVM itself is being built. LLVM 9 used to pass, but suddenly started breaking in cff49cb, and I needed to downgrade the dynamic tests to LLVM 8 with #490 in order to fix it again.

@elliottslaughter elliottslaughter changed the title Dynamic linked Terra breaks tests in LLVM 11 Dynamic linked Terra breaks tests in LLVM 9-11 Apr 22, 2021
@ProfFan
Copy link
Contributor

ProfFan commented Jul 15, 2021

To chime in after so many years :) I remember this before, and it's because LLVM is loaded twice. The reason why it's loaded twice, I don't remember, but should be inside some issue comments.

@elliottslaughter
Copy link
Member Author

This seems plausible, and I remember #357 (comment). I guess the question is still where the second copy of LLVM is coming from, since (at least at the moment) we're still statically linking Clang, and I don't think that would pull in a second copy by itself.

@ProfFan
Copy link
Contributor

ProfFan commented Jul 16, 2021

CastXML/CastXML#102

@elliottslaughter
Copy link
Member Author

This seems to have gone away with the upgrade to Ubuntu 18.04. In general, I've begun to suspect that the Ubuntu packages are simply higher quality; LLVM's own packages seem to have intermittent issues. I'm increasingly inclined to upgrade Ubuntu more aggressively so we can stick with newer first-party packages.

Anyway, #534 confirms that this works in LLVM 9 and 10, so I'm going to consider this fixed as soon as that merges.

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 a pull request may close this issue.

2 participants