-
Notifications
You must be signed in to change notification settings - Fork 530
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
Integrate LLVM at 6d38dbf6eb56fd2b3399565af455de96a99ffa0f #4103
base: main
Are you sure you want to change the base?
Conversation
1: [TOSA] Update rescale input_/output_zp and double_round attribute * Update tosa.rescale input_/output_zp as inputs according to TOSA 1.0 * Update double_round bool attribute to rounding_mode in alignment with TOSA 1.0. rounding_mode supports "SINGLE_ROUND", "INEXACT_ROUND", and "DOUBLE_ROUND". Existing double_round behaviours are mapped as followed: - double_round = true -> rounding_mode = "DOUBLE_ROUND" - double_round = false -> rounding_mode = "SINGLE_ROUND" 2: [TOSA] Update tosa.negate's zero-points to inputs Update LIT tests and XFAIL sets
This PR can't be merged until the issue is resolved as described here: #3504 (comment) |
I'm wondering if someone wrote a conversion from reshape to expand shape? I'll take a look to triage but might not have time to upstream a fix. |
The crash occurs because of an expand shape op that gets created in the pattern Because @MaheshRavishankar allowed accessing the output shape for |
Hi @vivekkhandelwal1 and @zjgarvey , is there a resolution for this blocking issue yet? Some of our works depend on these TOSA 1.0 updates aligned upstream, and it seems like this blocking issue is not related to TOSA. Can we maybe do an integration with an LLVM hash that doesn't include the breaking issue (with all TOSA updates included, still)? cc: @sjarus |
I just saw these patterns. We should just drop those |
Hi @MaheshRavishankar, can you please review this: llvm/llvm-project#134219? |
Hi @justin-ngo-arm, we should wait for the changes to be merged in LLVM and then we can do a more latest bump. |
Sounds good to me. Thank you for helping with this! |
Thanks a lot, @MaheshRavishankar and @vivekkhandelwal1 ! |
No description provided.