Skip to content

[SYCL] Adjust Driver and tests for addition of imf-bf16 library. #7917

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 20 commits into from
Jan 18, 2023

Conversation

rdeodhar
Copy link
Contributor

@rdeodhar rdeodhar commented Jan 4, 2023

This change adds the lib-imf-bf16 library into the libraries expected to be linked in by the Driver in various scenarios.

@rdeodhar rdeodhar requested a review from a team as a code owner January 4, 2023 17:29
@rdeodhar rdeodhar temporarily deployed to aws January 4, 2023 18:19 — with GitHub Actions Inactive
@rdeodhar rdeodhar marked this pull request as draft January 4, 2023 20:28
@rdeodhar rdeodhar temporarily deployed to aws January 4, 2023 21:01 — with GitHub Actions Inactive
// RUN: %clangxx -fsycl -fsycl-targets=spir64_x86_64,spir64_gen -Xsycl-target-backend=spir64_gen "-device gen9" %s -### 2>&1 \
// RUN: | FileCheck %s -check-prefix=BFLOAT16-FALLBACK-FALLBACK
// R UN: %clangxx -fsycl -fsycl-targets=spir64_x86_64,spir64_gen -Xsycl-target-backend=spir64_gen "-device gen9" %s -### 2>&1 \
// R UN: | FileCheck %s -check-prefix=BFLOAT16-FALLBACK-FALLBACK
Copy link
Contributor

Choose a reason for hiding this comment

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

What happened here? Looks like an unintentional space was added to the RUN:

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Somehow the full test passes locally but fails in CI.
I am trying to temporarily disable some tests to get to the root cause of the failure.

@rdeodhar rdeodhar temporarily deployed to aws January 4, 2023 22:15 — with GitHub Actions Inactive
@rdeodhar rdeodhar temporarily deployed to aws January 4, 2023 23:13 — with GitHub Actions Inactive
@rdeodhar rdeodhar temporarily deployed to aws January 5, 2023 00:34 — with GitHub Actions Inactive
@rdeodhar rdeodhar temporarily deployed to aws January 5, 2023 04:34 — with GitHub Actions Inactive
@rdeodhar rdeodhar temporarily deployed to aws January 5, 2023 05:04 — with GitHub Actions Inactive
@rdeodhar rdeodhar temporarily deployed to aws January 5, 2023 05:39 — with GitHub Actions Inactive
@rdeodhar rdeodhar temporarily deployed to aws January 5, 2023 06:09 — with GitHub Actions Inactive
@rdeodhar rdeodhar marked this pull request as ready for review January 5, 2023 17:17
@rdeodhar rdeodhar requested a review from mdtoguchi January 5, 2023 23:11
@rdeodhar
Copy link
Contributor Author

rdeodhar commented Jan 5, 2023

The one fail on AMD/HIP appears to be caused by use of the fp16 data type without checking that the GPU supports it.
There is no use of bfloat16 in the test.

// RUN: %clangxx -fsycl %s --sysroot=%S/Inputs/SYCL -### 2>&1 \
// RUN: | FileCheck %s -check-prefix=BFLOAT16

// test that fallback bfloat16 libraries are added in JIT mode with generic target
// RUN: %clangxx -fsycl -fsycl-targets=spir64 %s -### 2>&1 \
// Test that fallback bfloat16 libraries are added in JIT mode with \
Copy link
Contributor

Choose a reason for hiding this comment

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

The escape at the end of comment lines is not necessary

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Right. I'll remove them.

@rdeodhar rdeodhar requested a review from mdtoguchi January 9, 2023 16:11
@rdeodhar rdeodhar temporarily deployed to aws January 9, 2023 21:26 — with GitHub Actions Inactive
@rdeodhar rdeodhar temporarily deployed to aws January 12, 2023 04:37 — with GitHub Actions Inactive
@rdeodhar rdeodhar temporarily deployed to aws January 12, 2023 11:03 — with GitHub Actions Inactive
@rdeodhar rdeodhar temporarily deployed to aws January 13, 2023 16:33 — with GitHub Actions Inactive
@rdeodhar rdeodhar temporarily deployed to aws January 14, 2023 01:05 — with GitHub Actions Inactive
@rdeodhar rdeodhar temporarily deployed to aws January 14, 2023 07:12 — with GitHub Actions Inactive
@rdeodhar rdeodhar temporarily deployed to aws January 15, 2023 02:25 — with GitHub Actions Inactive
@rdeodhar rdeodhar temporarily deployed to aws January 15, 2023 08:30 — with GitHub Actions Inactive
@rdeodhar rdeodhar temporarily deployed to aws January 17, 2023 01:08 — with GitHub Actions Inactive
@rdeodhar rdeodhar temporarily deployed to aws January 17, 2023 01:39 — with GitHub Actions Inactive
@yubingex007-a11y yubingex007-a11y self-requested a review January 18, 2023 14:04
@yubingex007-a11y
Copy link
Contributor

yubingex007-a11y commented Jan 18, 2023

why we haven't merged this PR?
@mdtoguchi can you merge it on behalf of Rajiv?

@MrSidims MrSidims requested a review from a team January 18, 2023 14:26
@MrSidims
Copy link
Contributor

I believe only @intel/llvm-gatekeepers can merge PRs.

@MrSidims
Copy link
Contributor

MrSidims commented Jan 18, 2023

UPD: I'm taking it back, it's not unique for this PR failure

I'm not 100% sure, but it seems like this PR brings the following regression for CUDA:
Failed Tests (1):
SYCL :: BFloat16/bfloat16_builtins.cpp

@steffenlarsen
Copy link
Contributor

why we haven't merged this PR? @mdtoguchi can you merge it on behalf of Rajiv?

Changes have not yet been merged due to the failure. In accordance with the contribution guidelines unrelated failures should be mentioned and reasoning should be given for why it is unrelated, optimally with a link to a related issue and/or a PR addressing the unrelated failures.

@MrSidims
Copy link
Contributor

/verify with intel/llvm-test-suite#1495

@MrSidims
Copy link
Contributor

@steffenlarsen I see the test failing in other PRs like #8033 , #8026 and #8031

My best guess, that this PR that was merged previously also required the test update, which was not merged . I have started 'verify with' to check this claim.

@steffenlarsen
Copy link
Contributor

An issue has been opened for the failure: #8040

@MrSidims
Copy link
Contributor

@intel/llvm-gatekeepers guess we can merge this PR. The mentioned issue is known and reported and lucky guess with 'verify with' command makes the test to pass.

@bader bader merged commit eb09e73 into intel:sycl Jan 18, 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.

6 participants