Skip to content

Conversation

aarongreig
Copy link
Contributor

@aarongreig aarongreig commented Dec 14, 2023

LLVM testing intel/llvm#12481

@aarongreig aarongreig force-pushed the aaron/refactorHipEnqueueErrors branch 2 times, most recently from f614c49 to c451bf2 Compare December 15, 2023 10:52
@aarongreig aarongreig marked this pull request as ready for review December 15, 2023 10:52
@aarongreig aarongreig requested a review from a team as a code owner December 15, 2023 10:52
@aarongreig aarongreig requested a review from npmiller December 15, 2023 10:52
@aarongreig aarongreig force-pushed the aaron/refactorHipEnqueueErrors branch from c451bf2 to f837719 Compare December 15, 2023 11:27
@codecov-commenter
Copy link

codecov-commenter commented Dec 15, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (b66cf9b) 15.46% compared to head (f989b69) 15.46%.

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1190   +/-   ##
=======================================
  Coverage   15.46%   15.46%           
=======================================
  Files         238      238           
  Lines       33883    33883           
  Branches     3747     3747           
=======================================
  Hits         5239     5239           
  Misses      28593    28593           
  Partials       51       51           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Contributor

@hdelan hdelan left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Contributor

@jchlanda jchlanda left a comment

Choose a reason for hiding this comment

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

Really like this, needless accumulation of error codes in Result-like variables, instead of straight out returns, and not using UR_CHECK_ERROR are one of my top pet hates. Thank you!

@aarongreig aarongreig force-pushed the aaron/refactorHipEnqueueErrors branch from f837719 to 0011dd3 Compare January 23, 2024 10:33
@aarongreig
Copy link
Contributor Author

@npmiller please take a look when you can

Copy link
Contributor

@npmiller npmiller left a comment

Choose a reason for hiding this comment

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

LGTM, sorry about the late review!

@aarongreig aarongreig force-pushed the aaron/refactorHipEnqueueErrors branch from a2c1f16 to f989b69 Compare January 26, 2024 10:53
@kbenzie kbenzie added the hip HIP adapter specific issues label Apr 10, 2024
@aarongreig aarongreig force-pushed the aaron/refactorHipEnqueueErrors branch from f989b69 to 5ebd333 Compare September 25, 2024 16:30
// but currently unmapped advice arguments as not supported by this
// platform. Therefore, warn the user instead of throwing and aborting
// the runtime.
if (Result == UR_RESULT_ERROR_INVALID_ENUMERATION) {
Copy link
Contributor

@GeorgeWeb GeorgeWeb Sep 25, 2024

Choose a reason for hiding this comment

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

I may be missing something here but is this if (Result == UR_RESULT_ERROR_INVALID_ENUMERATION) meant to be checked again inside the above if (Result == UR_RESULT_ERROR_INVALID_ENUMERATION)? It is already true in this case. Was it meant to be wrapped in if (Result != UR_RESULT_SUCCESS) -> check if equals invalid then msg and return else throw?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think I messed up the rebase here, now it just falls through to UR_CHECK_ERROR(Result) if we aren't doing the adapter specific thing

Copy link
Contributor

Choose a reason for hiding this comment

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

Yeah that makes sense to me now. Thanks, I actually thuoght it must've been a dodgy rebase by the looks of it.

Copy link
Contributor

@GeorgeWeb GeorgeWeb left a comment

Choose a reason for hiding this comment

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

I know I am super late to the party here. Generally looks good. Thank you for cleaning that up!
Just a little comment I was confused about.

@aarongreig aarongreig added the ready to merge Added to PR's which are ready to merge label Sep 26, 2024
Mostly by taking the existing try/catch/UR_CHECK_ERROR based approach
and making sure it's used consistently so as not to drop any errors.
@aarongreig aarongreig force-pushed the aaron/refactorHipEnqueueErrors branch from d070776 to 96468e2 Compare October 3, 2024 10:49
@aarongreig aarongreig merged commit a9645bd into oneapi-src:main Oct 7, 2024
75 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hip HIP adapter specific issues ready to merge Added to PR's which are ready to merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants