Skip to content

[SYCL] Remove unused _PreviewBreakingChanges param from wrapSYCLBinaries#22663

Open
bviyer wants to merge 3 commits into
syclfrom
bviyer-fix-linux-dbg-build
Open

[SYCL] Remove unused _PreviewBreakingChanges param from wrapSYCLBinaries#22663
bviyer wants to merge 3 commits into
syclfrom
bviyer-fix-linux-dbg-build

Conversation

@bviyer

@bviyer bviyer commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

Remove unused _PreviewBreakingChanges parameter from wrapSYCLBinaries

The change removes the _PreviewBreakingChanges bool parameter (and the file-scoped PreviewBreakingChanges static) from wrapSYCLBinaries and its sole caller. The value was stored but never read.

…inaries

The change removes the _PreviewBreakingChanges bool parameter
(and the file-scoped PreviewBreakingChanges static) from
wrapSYCLBinaries and its sole caller. The value was stored
but never read.
@bviyer
bviyer requested a review from a team as a code owner July 17, 2026 17:30
@bviyer bviyer changed the title [SYCL] Remove unused _PreviewBreakingChanges parameter from wrapSYCLB… [SYCL] Remove unused _PreviewBreakingChanges param from wrapSYCLBinaries Jul 17, 2026
@bviyer
bviyer requested a review from YuriPlyakhin July 17, 2026 17:31

if (Error E = offloading::wrapSYCLBinaries(
M, Images, offloading::SYCLWrappingOptions(),
Args.hasArg(OPT_preview_breaking_changes)))

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

should we remove the opt from clang-linker-wrapper too?

def preview_breaking_changes : Flag<["-"], "fpreview-breaking-changes">,

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

maybe it is good to keep it, in case, we again will introduce breaking changes in the future.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

i dont have a stong opinion but usually i tend to favor removing code that isn't doing anything, i'll leave it up to Balaji.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

+1 for removing unused option.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

fixed.

@YuriPlyakhin YuriPlyakhin left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM

@sys-ce-bb

Copy link
Copy Markdown
Contributor

@intel/llvm-gatekeepers please consider merging

@bviyer
bviyer requested a review from bader July 17, 2026 21:41
@uditagarwal97

Copy link
Copy Markdown
Contributor

@intel/llvm-gatekeepers please consider merging

This commit will be authored by 43187390+bviyer@users.noreply.github.com.

Hi @bviyer,
Please check out https://llvm.org/docs/DeveloperPolicy.html#email-addresses - you'd have to change your Github account setting to allow committing from your personal/company email address. We don't allow committing from anonymous email addresses (like from noreply.github.com). Just changing your Github account settings should suffice - you don't have update the commits to include your personal email.
Thanks

@bviyer

bviyer commented Jul 17, 2026

Copy link
Copy Markdown
Contributor Author

@intel/llvm-gatekeepers please consider merging

This commit will be authored by 43187390+bviyer@users.noreply.github.com.

Hi @bviyer, Please check out https://llvm.org/docs/DeveloperPolicy.html#email-addresses - you'd have to change your Github account setting to allow committing from your personal/company email address. We don't allow committing from anonymous email addresses (like from noreply.github.com). Just changing your Github account settings should suffice - you don't have update the commits to include your personal email. Thanks

I fixed it.

@bviyer
bviyer requested a review from a team as a code owner July 17, 2026 23:25
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