public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/95763] Feature request: compiler warning if line width exceeds N symbols Date: Sat, 17 Apr 2021 21:36:26 +0000 [thread overview] Message-ID: <bug-95763-4-E3Lkv5foLr@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95763-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95763 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Severity|normal |enhancement Last reconfirmed| |2021-04-17 Ever confirmed|0 |1 --- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> --- I assume you are talking about stuff like: int t, t1, t2, t43, t55, t6, t7888888, t99999, t999876, t323434, ttsdgsdg, thfgd, tdfhghh, t354635463546; ? If so confirmed. I have not looked into how to do this and if this is normally not useful without a code style checker. Having a code style checker part of GCC would be a good long term really.
next prev parent reply other threads:[~2021-04-17 21:36 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-19 9:55 [Bug c++/95763] New: " hyena at hyena dot net.ee 2020-06-19 12:08 ` [Bug c++/95763] " redi at gcc dot gnu.org 2020-06-19 13:12 ` hyena at hyena dot net.ee 2020-06-19 14:42 ` joseph at codesourcery dot com 2020-06-19 14:55 ` jakub at gcc dot gnu.org 2021-04-17 21:36 ` pinskia at gcc dot gnu.org [this message] 2024-06-20 20:44 ` mlevine55 at bloomberg dot net
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-95763-4-E3Lkv5foLr@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).