public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/103812] New: -fcond-mismatch could use a testcase that covers its documented behavior better Date: Wed, 22 Dec 2021 21:34:35 +0000 [thread overview] Message-ID: <bug-103812-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103812 Bug ID: 103812 Summary: -fcond-mismatch could use a testcase that covers its documented behavior better Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: documentation Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: egallager at gcc dot gnu.org CC: jsm28 at gcc dot gnu.org Target Milestone: --- Continuing my current re-read of the GCC docs (from bug 103810), I came across the -fcond-mismatch option, the docs for which say: "Allow conditional expressions with mismatched types in the second and third arguments. The value of such an expression is void. This option is not supported for C++." https://gcc.gnu.org/onlinedocs/gcc/C-Dialect-Options.html#C-Dialect-Options However, the only place where I can find this option tested in the testsuite is in gcc/testsuite/gcc.dg/pch/valid-6.c, which doesn't contain any conditional expressions, it just includes a header (which doesn't contain any conditional expressions either), and defines a variable. Having a testcase that actually tests the feature being documented would be helpful for people looking to understand what its intended behavior is. (cc-ing last person to write a ChangeLog entry mentioning the option that I could find)
next reply other threads:[~2021-12-22 21:34 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-22 21:34 egallager at gcc dot gnu.org [this message] 2022-06-02 15:35 ` [Bug c/103812] " egallager 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-103812-4@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).