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/108701] Incorrect -Wmisleading-indentation Date: Tue, 07 Feb 2023 16:49:43 +0000 [thread overview] Message-ID: <bug-108701-4-jiI4mdIxUM@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108701-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108701 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |WAITING Last reconfirmed| |2023-02-07 Ever confirmed|0 |1 --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- -ftabstop=4 fixes the warning. Looks like godbolt is using 4 spaces/tab in their editor but GCC defaults to 8 spaces per tab. I suspect you need to supply -ftabstop=4 to override GCC's defaults if you are using 4space/tabs.
next prev parent reply other threads:[~2023-02-07 16:49 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-07 16:45 [Bug c/108701] New: " apjo at tuta dot io 2023-02-07 16:46 ` [Bug c/108701] " pinskia at gcc dot gnu.org 2023-02-07 16:49 ` pinskia at gcc dot gnu.org [this message] 2023-02-07 16:52 ` pinskia at gcc dot gnu.org 2023-02-07 16:55 ` pinskia at gcc dot gnu.org 2023-02-07 17:01 ` apjo at tuta dot io 2023-02-07 17:02 ` pinskia at gcc dot gnu.org 2023-02-07 17:05 ` apjo at tuta dot io 2023-02-07 17:09 ` pinskia at gcc dot gnu.org 2023-02-07 18:24 ` apjo at tuta dot io 2023-02-07 18:26 ` pinskia at gcc dot gnu.org 2023-02-07 18:31 ` pinskia at gcc dot gnu.org 2023-02-07 18:37 ` apjo at tuta dot io
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-108701-4-jiI4mdIxUM@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).