-
Notifications
You must be signed in to change notification settings - Fork 593
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
chore: use system linker in macOS #15407
Conversation
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. Still don't know why I ran into that weird issue.
We might need to double-check this before merging |
I've reproduced the same issue. 😕 This appears to be a long-standing issue of Some observations:
|
If |
Wow, so much magic! I think either of them works for us. I was once curious why |
Signed-off-by: Bugen Zhao <[email protected]>
96443b2
to
bca0844
Compare
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite. This stack of pull requests is managed by Graphite. Learn more about stacking. Join @BugenZhao and the rest of your teammates on Graphite |
|
I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
The performance of the system linker has improved a lot in Xcode 15 (shipped with macOS 14 and enabled by default). See https://news.ycombinator.com/item?id=36218330.
A simple benchmark on compiling
cmd_all
and linking the binary:I believe it could outperforms further more under the
release
profile.So let's switch to the system linker to improve the experience and reduce the number of dependencies.
Checklist
./risedev check
(or alias,./risedev c
)Documentation
Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.