[Bug c/103812] New: -fcond-mismatch could use a testcase that covers its documented behavior better

[Bug c/103812] New: -fcond-mismatch could use a testcase that covers its documented behavior better

[egallager at gcc dot gnu.org]

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)

[Bug c/103812] -fcond-mismatch could use a testcase that covers its documented behavior better

[egallager at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103812

Eric Gallager <egallager at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://gcc.gnu.org/bugzill
                   |                            |a/show_bug.cgi?id=13419

--- Comment #1 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Eric Gallager from comment #0)
> 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.

Apparently that testcase was added in r0-57604-g54e109edfba7de for the sake of
bug 13419...