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

[GSoC] Mark const variables using llvm.invariant.start #6706

Merged
merged 8 commits into from Aug 3, 2017
Merged

[GSoC] Mark const variables using llvm.invariant.start #6706

merged 8 commits into from Aug 3, 2017

Conversation

coodie
Copy link
Contributor

@coodie coodie commented Jul 14, 2017

This PR marks const variables using llvm.invariant.start.

I am not 100% sure if I check for constness correctly, I have huge difficulties understanding what chapel compiler is doing, @mppf should be able to see instantly if I add this in correct spots.

@mppf
Copy link
Member

mppf commented Jul 24, 2017

  • full local --llvm testing
  • full local --llvm --fast

Both of these fail runtime/sungeun/chpl-env-gen but that might happen on master...

@mppf
Copy link
Member

mppf commented Jul 26, 2017

Passed full local testing.

@mppf mppf merged commit a68e527 into chapel-lang:master Aug 3, 2017
mppf added a commit that referenced this pull request Aug 3, 2017
llvm.invariant.start tests

[PR by @coodie - reviewed/merged by @mppf]

This PR introduces tests for changes in #6706.

[New tests pass with an LLVM-enabled compiler]
@coodie coodie changed the title Mark const variables using llvm.invariant.start [GSoC] Mark const variables using llvm.invariant.start Aug 28, 2017
@mppf mppf mentioned this pull request Oct 3, 2017
7 tasks
@mppf mppf mentioned this pull request May 31, 2023
4 tasks
mppf added a commit that referenced this pull request May 31, 2023
This PR adjusts the Chapel code generator to not generate calls to
`llvm.invariant.start`. The reason for doing that is that we are seeing
test failures for some tests with `--fast` after upgrading to LLVM 15.
Generation of `llvm.invariant.start` was initially added in PR #6706.
I'd like to fix the problems with these in a better way than just not
generating `llvm.invariant.start`, but removing it for now is the
short-term solution in case I cannot come up with a fix in a reasonable
amount of time. Note that it is still possible to generate a call to one
of these with `PRIM_INVARIANT_START` but that is not done in any modules
or tests.

Reviewed by @riftEmber - thanks!

- [x] full comm=none --fast testing with a system LLVM 14
- [x] full comm=none --fast testing with a system LLVM 15
- [x] full comm=none testing with a system LLVM 14
- [x] full comm=none testing with a system LLVM 15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants