Skip to content

Conversation

@CyB3RC0nN0R
Copy link

@CyB3RC0nN0R CyB3RC0nN0R commented Aug 9, 2021

When compiling git without this workaround, cloning a remote repository results in a "bad object" error (the object in question seems to be random) most of the time.

I am experiencing this issue with the GCC versions 11.1.0-r2 and 11.2.0. I assume that it didn't exist before GCC 11, at least I didn't notice it until GentooLTO switched to GCC 11.

When compiling git without this workaround, cloning a remote repository results in a "bad object" error (the object in question seems to be random) most of the time.
@BorisCarvajal
Copy link

Thanks for the workaround.

I found this recent GCC report that seems to be the same issue:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101949

@CyB3RC0nN0R
Copy link
Author

I found this recent GCC report that seems to be the same issue:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101949

This seems to be it. They have already fixed it, so this PR is obsolete now. I will keep it for reference until the fix is available in the GCC version used by Gentoo LTO.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants