* Removing LLVM objtool warning filter @ 2024-12-20 20:06 Nathan Chancellor 2024-12-21 0:33 ` Philip Li 0 siblings, 1 reply; 4+ messages in thread From: Nathan Chancellor @ 2024-12-20 20:06 UTC (permalink / raw) To: Philip Li, lkp; +Cc: llvm, peterz, jpoimboe 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 (llvm@lists.linux.dev) 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 ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Removing LLVM objtool warning filter 2024-12-20 20:06 Removing LLVM objtool warning filter Nathan Chancellor @ 2024-12-21 0:33 ` Philip Li 2024-12-23 21:34 ` Nathan Chancellor 0 siblings, 1 reply; 4+ messages in thread From: Philip Li @ 2024-12-21 0:33 UTC (permalink / raw) To: Nathan Chancellor; +Cc: lkp, llvm, peterz, jpoimboe On Fri, Dec 20, 2024 at 01:06:17PM -0700, Nathan Chancellor wrote: > 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 (llvm@lists.linux.dev) 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 > > Cheers, > Nathan ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Removing LLVM objtool warning filter 2024-12-21 0:33 ` Philip Li @ 2024-12-23 21:34 ` Nathan Chancellor 2024-12-24 0:28 ` Philip Li 0 siblings, 1 reply; 4+ messages in thread From: Nathan Chancellor @ 2024-12-23 21:34 UTC (permalink / raw) To: Philip Li; +Cc: lkp, llvm, peterz, jpoimboe Hi Philip, On Sat, Dec 21, 2024 at 08:33:09AM +0800, Philip Li wrote: > On Fri, Dec 20, 2024 at 01:06:17PM -0700, Nathan Chancellor wrote: > > 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 (llvm@lists.linux.dev) 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. Thanks a lot! > 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 ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Removing LLVM objtool warning filter 2024-12-23 21:34 ` Nathan Chancellor @ 2024-12-24 0:28 ` Philip Li 0 siblings, 0 replies; 4+ messages in thread From: Philip Li @ 2024-12-24 0:28 UTC (permalink / raw) To: Nathan Chancellor; +Cc: lkp, llvm, peterz, jpoimboe On Mon, Dec 23, 2024 at 02:34:47PM -0700, Nathan Chancellor wrote: > Hi Philip, > > On Sat, Dec 21, 2024 at 08:33:09AM +0800, Philip Li wrote: > > On Fri, Dec 20, 2024 at 01:06:17PM -0700, Nathan Chancellor wrote: > > > 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 (llvm@lists.linux.dev) 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. > > Thanks a lot! > > > 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. > > Cheers, > Nathan ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2024-12-24 0:29 UTC | newest] Thread overview: 4+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2024-12-20 20:06 Removing LLVM objtool warning filter Nathan Chancellor 2024-12-21 0:33 ` Philip Li 2024-12-23 21:34 ` Nathan Chancellor 2024-12-24 0:28 ` Philip Li
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox