Skip to content

[NFC][SYCL] Don't use fprintf as deemed "unsafe" #18275

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.

Sign up for GitHub

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
Apr 30, 2025
Merged

[NFC][SYCL] Don't use fprintf as deemed "unsafe" #18275

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
82ca329
[NFC][SYCL] Don't use `fprintf` as deemed "unsafe"
aelovikov-intel Apr 25, 2025
4f8b757
Switch to `std::cerr`
aelovikov-intel Apr 30, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion sycl/include/sycl/accessor.hpp
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -236,7 +236,7 @@ template <typename... Ts>
void cannot_be_called_on_host([[maybe_unused]] const char *API,
Ts &&.../* ignore */) {
#ifndef __SYCL_DEVICE_ONLY__
std::fprintf(stderr, "%s cannot be called on host!\n", API);
std::cerr << API << " cannot be called on host!" << std::endl;
std::abort();
#endif
}
Expand Down