Conversation
|
@hatal175 , if you tried marking the TU as Matching, would it go through? |
|
It didn't. I think it had extra data in the .data section. |
|
I've no idea what segfaulted in the github build |
Report for GZ2E01 (46a11f2 - 43f0385)📈 Matched code: 79.62% (+0.06%, +6852 bytes) ✅ 34 new matches
...and 4 more new matches |
|
is the pch data actually being linked? cause objdiff is just going to show it for any TU that includes it now, making it a bit annoying to diff, but it shouldnt actually effect anything when trying to build due to it being stripped |
|
Maybe not. Still have no idea why it doesn't match.
…On Mon, Aug 25, 2025, 02:14 TakaRikka ***@***.***> wrote:
*TakaRikka* left a comment (zeldaret/tp#2602)
<#2602 (comment)>
is the pch data actually being linked? cause objdiff is just going to show
it for any TU that includes it now, making it a bit annoying to diff, but
it shouldnt actually effect anything when trying to build due to it being
stripped
—
Reply to this email directly, view it on GitHub
<#2602 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACYQXXJ36UDPENWZKDNWTOT3PJBL7AVCNFSM6AAAAACEWA6SKKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMJYGQ2DCNZUGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
@hatal175 , in |
|
Good catch. Kinda hard to work on data after pch change in objdiff. |
|
I pulled @LagoLunatic 's changes for objdiff locally, rebuilt objdiff, and I was able to view the diff easily. |
No description provided.