Skip to content

[SYCL][NFC] Minor update of upper limit attribute value #2953

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

Merged
merged 1 commit into from
Dec 28, 2020

Conversation

smanna12
Copy link
Contributor

This patch updates MaxValue of SYCLIntelSchedulerTargetFmaxMhz
attribute to be consistent with other FPGA attributes.

Before:
static unsigned getMaxValue() {
return 1048576;

After:
static unsigned getMaxValue() {
return 1024*1024;

The MaxValue(upper limit) is just an arbitrary high value.

Signed-off-by: Soumi Manna [email protected]

This patch updates MaxValue of SYCLIntelSchedulerTargetFmaxMhz
attribute to be consistent with other FPGA attributes.

Before:
static unsigned getMaxValue() {
      return 1048576;

After:
static unsigned getMaxValue() {
      return 1024*1024;

The MaxValue(upper limit) is just an arbitrary high value.

Signed-off-by: Soumi Manna <[email protected]>
@smanna12 smanna12 marked this pull request as ready for review December 25, 2020 00:27
@romanovvlad romanovvlad merged commit 0588075 into intel:sycl Dec 28, 2020
@smanna12 smanna12 deleted the UpdateMaxValue branch December 28, 2020 14:52
jsji pushed a commit that referenced this pull request Jan 26, 2025
In reverse translation always use poison values except cases where we translate OpUndef. In other cases common sense was used to define where it is safe to replace undef to poison (e.g. in creating structures, regularization passes).

This resolves #2953 and aligns us with the LLVM community in terms of generating IR.

Original commit:
KhronosGroup/SPIRV-LLVM-Translator@cec12d6cf46306d
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