public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/98630] Seg-fault when using a goto after condition (if) Date: Tue, 12 Jan 2021 10:43:42 +0000 [thread overview] Message-ID: <bug-98630-4-xuLFOyUOou@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98630-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98630 --- Comment #11 from Jakub Jelinek <jakub at gcc dot gnu.org> --- The reason why C++ has it as hard error is I think object construction/destruction, in C the warning is for code to be portable to C++, in plain C it is all about making sure variables are initialized, which users can do correctly even if they cross variable initialization. So in C there is nothing wrong per se on the crossing, just the warning can help if -Wuninitialized or -Wmaybe-uninitialized has false negatives as in this case.
next prev parent reply other threads:[~2021-01-12 10:43 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-11 22:48 [Bug c/98630] New: " k.even-mendoza at imperial dot ac.uk 2021-01-12 8:11 ` [Bug tree-optimization/98630] " rguenth at gcc dot gnu.org 2021-01-12 8:22 ` rguenth at gcc dot gnu.org 2021-01-12 8:26 ` rguenth at gcc dot gnu.org 2021-01-12 8:29 ` [Bug c/98630] " rguenth at gcc dot gnu.org 2021-01-12 8:50 ` k.even-mendoza at imperial dot ac.uk 2021-01-12 8:51 ` k.even-mendoza at imperial dot ac.uk 2021-01-12 10:08 ` jakub at gcc dot gnu.org 2021-01-12 10:16 ` jakub at gcc dot gnu.org 2021-01-12 10:33 ` rguenth at gcc dot gnu.org 2021-01-12 10:40 ` jakub at gcc dot gnu.org 2021-01-12 10:43 ` jakub at gcc dot gnu.org [this message] 2021-01-12 14:34 ` k.even-mendoza at imperial dot ac.uk 2021-01-12 14:39 ` jakub at gcc dot gnu.org 2021-01-12 14:42 ` k.even-mendoza at imperial dot ac.uk 2021-01-12 14:44 ` jakub at gcc dot gnu.org
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-98630-4-xuLFOyUOou@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).