-
Notifications
You must be signed in to change notification settings - Fork 415
Enable glibc-compatibility on arm #6572
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
Conversation
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
/hold |
/run-all-tests |
/cc @solotzg @windtalker |
Can you help to investigate whether we can remove this func safely ? tiflash/libs/libglibc-compatibility/glibc-compatibility.c Lines 27 to 30 in eaf1a4c
|
okk, I will |
I think we can not remove it before we manually designate the signal stack. However, the returned value could be changed to 16KiB, so that we can save many VSZ. Morever, though we can use SIGSTKSZ to define the size of signal stack, it's too small to collect enough information. |
size_t __pthread_get_minstack(const pthread_attr_t * attr) | ||
{ | ||
return 1048576; /// This is a guess. Don't sure it is correct. | ||
return 16384; /// This is a guess. Don't sure it is correct. |
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.
Please update comment and add explanation.
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.
Please update comment and add explanation.
done
lgtm |
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
/unhold |
/run-all-tests |
/run-all-tests |
/merge |
@windtalker: It seems you want to merge this PR, I will help you trigger all the tests: /run-all-tests You only need to trigger If you have any questions about the PR merge process, please refer to pr process. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
@windtalker: In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
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
/merge |
@windtalker: It seems you want to merge this PR, I will help you trigger all the tests: /run-all-tests You only need to trigger If you have any questions about the PR merge process, please refer to pr process. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
This pull request has been accepted and is ready to merge. Commit hash: 5b63cb7
|
/merge |
@LittleFall: It seems you want to merge this PR, I will help you trigger all the tests: /run-all-tests You only need to trigger If you have any questions about the PR merge process, please refer to pr process. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
@xzhangxian1008: Your PR was out of date, I have automatically updated it for you. At the same time I will also trigger all tests for you: /run-all-tests
If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
/run-unit-test |
close pingcap#6571 Signed-off-by: ywqzzy <[email protected]>
/cherry-pick release-6.5 |
@wuhuizuo: new pull request created to branch In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
/cherry-pick release-6.1 |
Signed-off-by: ti-chi-bot <[email protected]>
@xzhangxian1008: new pull request created to branch In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
close #6571 Co-authored-by: xzhangxian1008 <[email protected]>
close #6571 Signed-off-by: ti-chi-bot <[email protected]> Co-authored-by: xzhangxian1008 <[email protected]>
What problem does this PR solve?
Issue Number: close #6571
Problem Summary:
What is changed and how it works?
Check List
Tests
Side effects
Documentation
Release note