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

Remove CL_CONTEXT_COMPILER_MODE_SIMULATION_INTELFPGA #244

Merged
merged 1 commit into from
Jan 20, 2023

Conversation

intel-liudean
Copy link
Contributor

@intel-liudean intel-liudean commented Jan 13, 2023

This compiler mode (mode 6) is unused by the runtime, safe to remove.

When we search for the compiler mode on Google, nothing returned, so it's also not documented anywhere.

Tests Done:
Runtime Unit Tests
Checked that products/regtest/hld does not have lines like "compiler_mode => 6" or "compiler_mode => '6'"

sophimao
sophimao previously approved these changes Jan 13, 2023
Copy link
Contributor

@sophimao sophimao left a comment

Choose a reason for hiding this comment

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

Thanks Dean! Looks good to me :)

Another thing is that I tried search for the compiler mode on Google but nothing returned, so it's also not documented anywhere. Not sure if this is worth mentioning in the PR description?

@intel-liudean
Copy link
Contributor Author

intel-liudean commented Jan 13, 2023

I will mention it, I think there is no down side by mentioning it.

Copy link
Contributor

@pcolberg pcolberg left a comment

Choose a reason for hiding this comment

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

Thanks @intel-liudean, and thanks @sophimao for the review. @intel-liudean, please include a description in the commit message that details why you are making the change and why the change does not cause a regression. We merge commits as is, which means the pull-request description is (mostly) irrelevant whereas the commit message is important.

Note that you won't be able to find the compiler modes via public searches since the compiler code has not been open-sourced; and unfortunately the mode uses numeric values which are hard to search for.

@sophimao
Copy link
Contributor

Thanks @pcolberg for the comment! It appears to me that the compiler mode here is only used in runtime though, unless I'm missing something? But you are right, it's probably hard to look for those with public searches.

@intel-liudean
Copy link
Contributor Author

I have included a description in the commit message for 1) why I am making this change and 2) what tests I have done to make sure no regression happens.

This compiler mode (simulation mode, mode 6) is unused by the runtime and hence safe to remove. I am removing it so that the differences between simulation devices and hardware devices are removed as much as possible.

When we search for the compiler mode on Google, nothing returned, so it's also not documented anywhere.

Tests Done:
Runtime Unit Tests
Checked that products/regtest/hld does not have lines like "compiler_mode => 6" or "compiler_mode => '6'"
@intel-liudean intel-liudean force-pushed the simulation-device-selector branch from 67c8238 to 320d4cc Compare January 13, 2023 21:35
Copy link
Contributor

@pcolberg pcolberg left a comment

Choose a reason for hiding this comment

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

Perfect, thanks @intel-liudean! I will merge this once the integration test is complete.

@pcolberg pcolberg merged commit 2425af6 into intel:main Jan 20, 2023
@intel-liudean
Copy link
Contributor Author

Thank you @pcolberg for merging this change!

@pcolberg pcolberg added this to the 2023.2 milestone Jan 31, 2023
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