match: Fix some `(op (cnd @0 @1 @2) @3)` patterns [PR123778]

match: Fix some `(op (cnd @0 @1 @2) @3)` patterns [PR123778]

All of these patterns have in common is they try to move
the op inside the cnd if it simplifies. The problem is the
type of the op does not need to be the type of first operand
and instead is the type of the type variable. The fix is to
supply the type to the op like in `(op:type @1 @3)`.
But since they were originally in the `(op! @1 @3)`, it should be:
`(op!:type @1 @3)`. Though this would be rejected as we don't pick
up the next token after parsing the `!` (note `^` has the same issue
which is also fixed here too).

Bootstrapped and tested on x86_64-linux-gnu.

	PR tree-optimization/123778

gcc/ChangeLog:

	* genmatch.cc (parser::parse_expr): Peek on the next
	token after eating the `!` or `^`.
	* match.pd (`(op (cnd @0 @1 @2) @3)`, `(op @3 (cnd @0 @1 @2))`):
	Add the type to resulting op.

gcc/testsuite/ChangeLog:

	* gcc.dg/torture/pr123778-1.c: New test.

Signed-off-by: Andrew Pinski <andrew.pinski@oss.qualcomm.com>