DIAGTOOL(1)

πŸ’– DIAGTOOL(1) β€” the clang diagnostics tool, bestie edition πŸ’–

okay so picture this: it's page 1 of the manual, the source is Clang, and the whole vibe is "let's actually figure out what clang's diagnostics are doing." welcome to diagtool. πŸŽ€


✨ NAME ✨

diagtool β€” the clang diagnostics tool. that's it, that's the name, short and iconic. πŸ‘‘


🌸 SYNOPSIS 🌸

diagtool command [args]

πŸ¦‹ DESCRIPTION πŸ¦‹

diagtool is literally a combination of four tools for dealing with diagnostics in clang. four. a whole squad. 🫢


πŸ’… SUBCOMMANDS πŸ’…

diagtool is separated into several subcommands, and each one is tailored to a different purpose (main character energy, each of them). here's a lil summary of every command, and the deets come in the sections right after. ✨

  • find-diagnostic-id β€” print the id of the given diagnostic. πŸ”
  • list-warnings β€” list warnings and their corresponding flags. πŸ“‹
  • show-enabled β€” show which warnings are enabled for a given command line. βœ…
  • tree β€” show warning flags in a tree view. 🌳

πŸ“ find-diagnostic-id πŸ“

diagtool find-diagnostic-id diagnostic-name

🌈 list-warnings 🌈

diagtool list-warnings

πŸ’œ show-enabled πŸ’œ

diagtool show-enabled [options] filename ...

🧚 tree 🧚

diagtool tree [diagnostic-group]

⭐ AUTHOR ⭐

maintained by the Clang / LLVM Team (<http://clang.llvm.org>). they're keeping the lights on, no cap. πŸ™


2007-2026, The Clang Team. periodt. πŸ’–


and that's the whole page, bestie β€” Clang, version 19, dated Mar 11, 2026, and it's DIAGTOOL(1) all the way down. go forth and vibe check ur diagnostics βœ¨πŸ’…πŸ¦‹

πŸ“¦ where this page comes from