https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112374
--- Comment #20 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #19)
> enum E { F } a, b;
> char c;
> bool d;
> int e;
> int (*f) (int, int);
> int foo (int, int);
>
> void
> bar (void)
> {
> if (d)
> for (e = 0; c; e++ && a) switch (b) case F:
> f = foo;
> }
>
> ./xgcc -B ./ -fcompare-debug -O2 -march=skylake-avx512 -S pr112374.C
> xgcc: error: pr112374.C: ‘-fcompare-debug’ failure
> Though, that is because of different discriminators, so feels to be
> https://gcc.gnu.org/pipermail/gcc-patches/2022-October/603673.html
> related.
My reduced testcase:
```
extern const unsigned char mode_class[2];
extern int gen_reg_rtx (int);
int gen_lowpart (int, int);
void ix86_avx256_split_vector_move_misalign (int op0, int op1, unsigned code,
int mode) {
switch (mode_class[mode])
{
case 1:
if (mode != 1) { if (code != 0) { op0 = gen_reg_rtx (1); } op1 =
gen_lowpart (1, op1); } break;
}
}
```
Note the if and branch are all on the same line. And yes that seems like a
statement-frontiers issue too.
> Guess I'll start another reduction with additional -gno-statement-frontiers.
Likewise.
