This is an archive of the discontinued LLVM Phabricator instance.

Revert "[tsan] Fix GCC 8.3 build after D107911"
ClosedPublic

Authored by melver on Aug 17 2021, 1:21 AM.

Details

Summary

This reverts commit 797fe59e6b9512652c0ae5a6b69a3c6f5a573fcd.

The use of "EventType type : 3" is replicated for all Event structs and
therefore was still present. As a result this still caused failures on
older GCCs (9.2 or 8.3 or earlier).

The particular bot that was failing due to buggy GCC was fixed by
fef39cc472a773fae4761deaab1c701024ad13ec.

Therefore, no reason to keep the workaround around; revert it.

Diff Detail

Event Timeline

melver requested review of this revision.Aug 17 2021, 1:21 AM
melver created this revision.
Herald added a project: Restricted Project. · View Herald TranscriptAug 17 2021, 1:21 AM
Herald added a subscriber: Restricted Project. · View Herald Transcript
vitalybuka accepted this revision.Aug 17 2021, 9:52 AM

I just realized it's GO only. Any idea why this did not report on regular tsan builds? We have 8.3 on our bots.

This revision is now accepted and ready to land.Aug 17 2021, 9:52 AM

I just realized it's GO only. Any idea why this did not report on regular tsan builds? We have 8.3 on our bots.

It seems GCC has tons of warnings by default (even when I use latest GCC), and so enabling Werror on GCC just seems impossible. Checking the bot's script, it looks like Werror is only enabled when using self-hosted Clang:

I see this comment:

# Use both gcc and just-built Clang/LLD as a host compiler/linker for sanitizer                                                                                                                                                                                
# tests. Assume that self-hosted build tree should compile with -Werror.
This revision was automatically updated to reflect the committed changes.