-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Add unwind information in huf_decompress_amd64.S #4367
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
base: dev
Are you sure you want to change the base?
Conversation
Hi @al13n321! Thank you for your pull request. We require contributors to sign our Contributor License Agreement, and yours needs attention. You currently have a record in our system, but the CLA is no longer valid, and will need to be resubmitted. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at [email protected]. Thanks! |
Btw, I'm confused: you guys at Meta use profilers (I used to use strobelight a lot), and zstd decompression probably takes a good fraction of cpu time in a lot of Meta software. Surely many people would notice if stack unwinding doesn't work well on zstd decompression? Why wasn't this already fixed ages ago? I'm probably missing something. |
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks! |
cc @terrelln |
I am a big fan of this change. @MatzeB and I were just chatting about this issue a few weeks ago. This would be a great improvement IMO. |
I mentioned a while ago that we need frame pointers (aka rbp) to be setup for the profilers in our company. For all I know our profiling tools don't interpret unwind tables for performance reasons, so this change in itself won't help our setup. Of course adding proper unwind table information is a great idea regardless. |
Sounds good @embg ! Also there were a few test failures blocking this merge, |
Rebased. |
These two asm functions clobber
rbp
register (aka omit frame pointer), but didn't provide stack unwinding information. So stack traces in profilers and debuggers couldn't go past these functions. This PR adds the unwind information, in a straightforward way.I tested it with one profiler (ClickHouse's built-in query profiler, uses libunwind) and one debugger (https://github.com/al13n321/nnd), both managed to unwind through this function with this fix.