Skip to content

[SYCL] Allow __glibcxx_assert_fail in SemaSYCL #18856

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 2 commits into from
Jun 11, 2025

Conversation

jinge90
Copy link
Contributor

@jinge90 jinge90 commented Jun 9, 2025

GCC-15 introduced __glibcxx_assert_fail function used in -O0 for many STL functions' runtime check. Its behavior is similar to normal 'assert', so we have supported it in libdevice in the same way as 'assert'. However, compfail will happen in some scenario reporting "undefined function without SYCL_EXTERNAL" error for "__glibcxx_assert_fail" declared in c++config.h, we have to allow this as exception in SemaSYCL.

@jinge90 jinge90 requested a review from a team as a code owner June 9, 2025 06:14
@jinge90 jinge90 marked this pull request as draft June 9, 2025 06:14
@jinge90 jinge90 temporarily deployed to WindowsCILock June 9, 2025 06:14 — with GitHub Actions Inactive
@jinge90 jinge90 temporarily deployed to WindowsCILock June 9, 2025 06:44 — with GitHub Actions Inactive
@jinge90 jinge90 temporarily deployed to WindowsCILock June 9, 2025 06:44 — with GitHub Actions Inactive
@jinge90 jinge90 temporarily deployed to WindowsCILock June 9, 2025 06:58 — with GitHub Actions Inactive
@jinge90 jinge90 marked this pull request as ready for review June 9, 2025 07:13
Signed-off-by: jinge90 <[email protected]>
@jinge90 jinge90 temporarily deployed to WindowsCILock June 9, 2025 07:29 — with GitHub Actions Inactive
@jinge90 jinge90 temporarily deployed to WindowsCILock June 9, 2025 07:29 — with GitHub Actions Inactive
Comment on lines +615 to +626
if (IsAllowed)
return true;

// GCC-15 introduced "std::__glibcxx_assert_fail" declared c++config.h and
// extensively used in STL to do runtime check in debug mode. The behavior
// is similar to "assert", we have supported it in libdevice in the same way
// as "assert". However, Sema check will report "undefined function without
// SYCL_EXTERNAL attribute" error in some cases. We have to allow it just as
// what we did to "__failed_assertion". The prototype is following:
// void __glibcxx_assert_fail(const char *, int, const char *, const char*);
IsAllowed = (Callee->getName() == GlibcxxAssertFail) &&
Callee->getNumParams() == 4 &&
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
if (IsAllowed)
return true;
// GCC-15 introduced "std::__glibcxx_assert_fail" declared c++config.h and
// extensively used in STL to do runtime check in debug mode. The behavior
// is similar to "assert", we have supported it in libdevice in the same way
// as "assert". However, Sema check will report "undefined function without
// SYCL_EXTERNAL attribute" error in some cases. We have to allow it just as
// what we did to "__failed_assertion". The prototype is following:
// void __glibcxx_assert_fail(const char *, int, const char *, const char*);
IsAllowed = (Callee->getName() == GlibcxxAssertFail) &&
Callee->getNumParams() == 4 &&
// GCC-15 introduced "std::__glibcxx_assert_fail" declared c++config.h and
// extensively used in STL to do runtime check in debug mode. The behavior
// is similar to "assert", we have supported it in libdevice in the same way
// as "assert". However, Sema check will report "undefined function without
// SYCL_EXTERNAL attribute" error in some cases. We have to allow it just as
// what we did to "__failed_assertion". The prototype is following:
// void __glibcxx_assert_fail(const char *, int, const char *, const char*);
IsAllowed = IsAllowed || (Callee->getName() == GlibcxxAssertFail) &&
Callee->getNumParams() == 4 &&

Copy link
Contributor

Choose a reason for hiding this comment

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

Just a nit.

@jinge90
Copy link
Contributor Author

jinge90 commented Jun 10, 2025

Hi, @intel/dpcpp-cfe-reviewers
Could you take a look?
Thanks very much.

@jinge90
Copy link
Contributor Author

jinge90 commented Jun 11, 2025

Hi, @intel/dpcpp-cfe-reviewers
Ping~

@jinge90 jinge90 requested a review from a team June 11, 2025 09:25
@jinge90
Copy link
Contributor Author

jinge90 commented Jun 11, 2025

Hi, @intel/llvm-gatekeepers
Could you help merge this PR?
Thanks very much!

@sommerlukas
Copy link
Contributor

Has the nit from @yingcong-wu been addressed?

@yingcong-wu
Copy link
Contributor

Has the nit from @yingcong-wu been addressed?

As in the comment, it is just a nit. I am fine with the current implementation as is.

@sommerlukas sommerlukas merged commit bd74453 into intel:sycl Jun 11, 2025
24 checks passed
@sommerlukas
Copy link
Contributor

Has the nit from @yingcong-wu been addressed?

As in the comment, it is just a nit. I am fine with the current implementation as is.

Ok, I've merged. In the future, please use "Approve" in these cases to make it easier for gatekeepers to assess the status of a PR.

@yingcong-wu
Copy link
Contributor

Has the nit from @yingcong-wu been addressed?

As in the comment, it is just a nit. I am fine with the current implementation as is.

Ok, I've merged. In the future, please use "Approve" in these cases to make it easier for gatekeepers to assess the status of a PR.

Will do, thank you.

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.

4 participants