Skip to contentSkip to conversation

Removing LLVM objtool warning filter

DISCUSSION Nathan Chancellor 2 participants 4 messages Dec 20, 2024 – Dec 24, 2024

lore
Share & tools
lore
#0 lore raw

Hi Philip and other LKP folks,

At some point, I believe there was a filter set up so that reports of objtool warnings that appear in clang builds were sent only to our mailing list ([email protected]) for triage. At this point, we believe it is best to treat those reports like other objtool reports and send them to the author of the change that introduced the warning with our list on CC in case people think it is a compiler bug or need further help understanding what is going on. Is that possible?

Cheers,
Nathan

#1 lore raw
Quoted 9 lines · Nathan Chancellor

Hi Philip and other LKP folks,

At some point, I believe there was a filter set up so that reports of objtool warnings that appear in clang builds were sent only to our mailing list ([email protected]) for triage. At this point, we believe it is best to treat those reports like other objtool reports and send them to the author of the change that introduced the warning with our list on CC in case people think it is a compiler bug or need further help understanding what is going on. Is that possible?

Got it Nathan, I will update the bot to send out this warning to author and cc llvm list, same as other warnings from clang.

Just to confirm, is it applied to all clang version or only latest one like clang 19/20?

Thanks

Quoted 3 lines

Cheers,
Nathan

#2 lore raw

Hi Philip,

Quoted 11 lines · Philip Li
Quoted 9 lines · Nathan Chancellor

Hi Philip and other LKP folks,

At some point, I believe there was a filter set up so that reports of objtool warnings that appear in clang builds were sent only to our mailing list ([email protected]) for triage. At this point, we believe it is best to treat those reports like other objtool reports and send them to the author of the change that introduced the warning with our list on CC in case people think it is a compiler bug or need further help understanding what is going on. Is that possible?

Quoted 2 lines

Got it Nathan, I will update the bot to send out this warning to author and cc llvm list, same as other warnings from clang.

Thanks a lot!

Quoted 2 lines

Just to confirm, is it applied to all clang version or only latest one like clang 19/20?

Let's do all clang versions and see how noisy it is. If we need to scale it back to just the latest, we can definitely do so.

Cheers,
Nathan

#3 lore raw
Quoted 17 lines · Nathan Chancellor

Hi Philip,

Quoted 11 lines · Philip Li
Quoted 9 lines · Nathan Chancellor

Hi Philip and other LKP folks,

At some point, I believe there was a filter set up so that reports of objtool warnings that appear in clang builds were sent only to our mailing list ([email protected]) for triage. At this point, we believe it is best to treat those reports like other objtool reports and send them to the author of the change that introduced the warning with our list on CC in case people think it is a compiler bug or need further help understanding what is going on. Is that possible?

Quoted 2 lines

Got it Nathan, I will update the bot to send out this warning to author and cc llvm list, same as other warnings from clang.

Quoted 7 lines

Thanks a lot!

Quoted 2 lines

Just to confirm, is it applied to all clang version or only latest one like clang 19/20?

Let's do all clang versions and see how noisy it is. If we need to scale it back to just the latest, we can definitely do so.

Got it, thanks for confirmation.

Quoted 3 lines

Cheers,
Nathan