-
Notifications
You must be signed in to change notification settings - Fork 30.4k
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
[PGO] [BUILD] Compilation fails with --enable-pgo-use #55852
Comments
Can you reproduce this without the external installation script? Just by building manually? |
can you open an issue to github.com/ada-url/ada? any ideas @lemire? |
I have checked right now, if disabling shared-zlib helps, since we recently switched to zlib-ng, but that does not seem to help. |
Here is also the complete build log, in case you need it. |
The reporter gets a warning due to Here is the GCC documentation
The most likely explanation is that user is using profile data from one version of the source, and then (likely by accident) trying to use it for profile-guided optimization with another version of the source code. |
Yes, this helps. Thank you :) |
FYI, I still think that the upstream ada project shouldnt kill the pgo compilation due that. Having mismatches with the PGO profile is pretty common. |
The issue is not due to ada. Ada does not kill PGO compilation. Within Node.js, ada is just two source files. It does not know anything about PGO. As far as I can tell, the ada library appears to be causing the problem, but it is not. Or rather, it is merely the fact that some C++ functions within ada were changed between the time you acquired the profile and the time you attempted a PGO-guided built. The PGO support is provided by Node.js. -Wno-error=coverage-mismatch when the flag --enable-pgo-use is enabled, but that is a Node.js issue. The flag Notice how it does not turn on I understand that you want, by default, to be able to do PGO built with profile data acquired from an older version of the code. So you want the flag If you want this change, I recommend you prepare a Node.js pull request with a justification. |
Version
23.2.0
Platform
Subsystem
No response
What steps will reproduce the bug?
Archlinux enviroment:
How often does it reproduce? Is there a required condition?
All time
What is the expected behavior? Why is that the expected behavior?
Compilation is successful
What do you see instead?
The profile is gathered with "make test". See here:
https://github.com/CachyOS/CachyOS-PKGBUILDS/blob/master/nodejs/PKGBUILD#L53-L83
This issue has been started with node 23.1 - before the compilation was successful
Compilation fails at the second compilation with the PGO profile:
Additional information
No response
The text was updated successfully, but these errors were encountered: