Skip to content

[SYCL] Properly take care of unnamed lambdas #827

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 1 commit into from
Nov 15, 2019

Conversation

alexbatashev
Copy link
Contributor

@alexbatashev alexbatashev commented Nov 13, 2019

When two lambdas with the same signature but different content are
submitted to queue, compiler complains about duplicate names and
finishes with error. This patch introduces a more correct way to mangle lambdas.

Signed-off-by: Alexander Batashev [email protected]

@alexbatashev alexbatashev force-pushed the private/abatashe/unnamed_lambda branch from f1719a7 to 6890eab Compare November 13, 2019 07:50
@alexbatashev alexbatashev force-pushed the private/abatashe/unnamed_lambda branch from 6890eab to 0720a75 Compare November 13, 2019 08:25
@bader
Copy link
Contributor

bader commented Nov 13, 2019

When two lambdas with the same signature but different content are submitted to queue, compiler crashes.

Why?

@jbrodman
Copy link
Contributor

@bader - We've not observed crashes so much as the compiler generating duplicate names and erroring out.

@alexbatashev alexbatashev force-pushed the private/abatashe/unnamed_lambda branch 2 times, most recently from 57f3596 to a7048b7 Compare November 14, 2019 07:52
@alexbatashev
Copy link
Contributor Author

When two lambdas with the same signature but different content are submitted to queue, compiler crashes.

Why?

I improved wording

@alexbatashev
Copy link
Contributor Author

After offline discussion with @rolandschulz I reconsidered the way to fix the problem.

Copy link
Contributor

@AGindinson AGindinson left a comment

Choose a reason for hiding this comment

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

Minor nits

@alexbatashev alexbatashev force-pushed the private/abatashe/unnamed_lambda branch from a7048b7 to ec30361 Compare November 14, 2019 14:09
rolandschulz
rolandschulz previously approved these changes Nov 14, 2019
Copy link
Contributor

@rolandschulz rolandschulz left a comment

Choose a reason for hiding this comment

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

pending the one remaining nit

When two lambdas with the same signature but different content are
submitted to queue, compiler complains about duplicate names and
finishes with error. This patch introduces a more correct way to mangle lambdas.

Signed-off-by: Alexander Batashev <[email protected]>
@bader bader merged commit d6aa11b into intel:sycl Nov 15, 2019
vmaksimo pushed a commit to vmaksimo/llvm that referenced this pull request Nov 30, 2020
Added translation of VCFCEntry kernel attribute to execution mode
VectorComputeFastCompositeKernelINTEL
@alexbatashev alexbatashev deleted the private/abatashe/unnamed_lambda branch July 28, 2021 06:43
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