-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
[improve](ub) fix some runtime error of ubsan when downcast #35343
Conversation
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
run buildall |
clang-tidy review says "All clean, LGTM! 👍" |
643b8de
to
90bcb47
Compare
clang-tidy review says "All clean, LGTM! 👍" |
run buildall |
clang-tidy review says "All clean, LGTM! 👍" |
TPC-H: Total hot run time: 41265 ms
|
TeamCity be ut coverage result: |
TPC-DS: Total hot run time: 168477 ms
|
ClickBench: Total hot run time: 30.86 s
|
run buildall |
TPC-H: Total hot run time: 41959 ms
|
TPC-DS: Total hot run time: 168844 ms
|
ClickBench: Total hot run time: 30.09 s
|
TeamCity be ut coverage result: |
PR approved by anyone and no changes requested. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
PR approved by at least one committer and no changes requested. |
those code could work well, but it will be report some runtime error under UBSAN, so refactor it to let's ubsan could running happy.
…5343) those code could work well, but it will be report some runtime error under UBSAN, so refactor it to let's ubsan could running happy.
those code could work well, but it will be report some runtime error under UBSAN, so refactor it to let's ubsan could running happy.
Proposed changes
those code could work well, but it will be report some runtime error under UBSAN,
so refactor it to let's ubsan could running happy.
Issue Number: close #xxx
Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...