Skip to content

Conversation

@jandres742
Copy link
Contributor

If piProgramBuild fails, do not remove L0 build log, which is expected to be read later in piProgramGetBuildInfo.

If piProgramBuild fails, do not remove L0 build log, which is
expected to be read later in piProgramGetBuildInfo.

Signed-off-by: Jaime Arteaga <jaime.a.arteaga.molina@intel.com>
@jandres742 jandres742 temporarily deployed to aws June 20, 2023 00:16 — with GitHub Actions Inactive
@jandres742 jandres742 temporarily deployed to aws June 20, 2023 00:54 — with GitHub Actions Inactive
@jandres742
Copy link
Contributor Author

changes are specific to L0, and the failure is on CUDA suite, so unrelated.

@jandres742 jandres742 marked this pull request as ready for review June 20, 2023 01:04
@jandres742 jandres742 requested a review from a team as a code owner June 20, 2023 01:04
@smaslov-intel
Copy link
Contributor

@jandres742 : this was already fixed in #8848
Any idea where had it gone? Also, are you destroying the log in piProgramGetBuildInfo?

@jandres742
Copy link
Contributor Author

@jandres742 : this was already fixed in #8848 Any idea where had it gone? Also, are you destroying the log in piProgramGetBuildInfo?

@smaslov-intel : yes, it is destroyed later in urProgramGetBuildInfo after printing the string, and also on program destructor.

This seems to have been an error introduced during the porting to UR, which was done after the #8848 PR you mentioned.

@againull againull merged commit b7ffbc7 into intel:sycl Jun 20, 2023
veselypeta pushed a commit to veselypeta/llvm that referenced this pull request Sep 21, 2023
If piProgramBuild fails, do not remove L0 build log, which is expected
to be read later in piProgramGetBuildInfo.

Signed-off-by: Jaime Arteaga <jaime.a.arteaga.molina@intel.com>
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