subject:"\[Bug target\/104901\] gcc\/config\/rs6000\/mm_malloc.h\:46\: incorrectLogicOperator"

[Bug target/104901] gcc/config/rs6000/mm_malloc.h:46: incorrectLogicOperator

2022-03-21 Thread segher at gcc dot gnu.org via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104901 --- Comment #11 from Segher Boessenkool --- $ cat vcc.c int f(int x) { return x == 31 && x == 42; } -Wlogical-op gives vcc.c: In function 'f': vcc.c:1:31: warning: logical 'and' of mutually exclusive tests is always false [-Wlogical-op] 1

[Bug target/104901] gcc/config/rs6000/mm_malloc.h:46: incorrectLogicOperator

2022-03-21 Thread schwab--- via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104901 --- Comment #10 from Andreas Schwab --- The values depend on the target, but they are genuine compile time constants.

[Bug target/104901] gcc/config/rs6000/mm_malloc.h:46: incorrectLogicOperator

2022-03-21 Thread dcb314 at hotmail dot com via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104901 --- Comment #9 from David Binderman --- (In reply to Andreas Schwab from comment #7) > I think it would still be worthwhile to avoid the antipattern (v == c1 && v > == c2). +1 I haven't got a rs6000 box, but I suspect our old friend -Wlogical-

[Bug target/104901] gcc/config/rs6000/mm_malloc.h:46: incorrectLogicOperator

2022-03-21 Thread segher at gcc dot gnu.org via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104901 --- Comment #8 from Segher Boessenkool --- Sure, but c1 as well as c2 are not constants here!

[Bug target/104901] gcc/config/rs6000/mm_malloc.h:46: incorrectLogicOperator

2022-03-21 Thread schwab--- via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104901 --- Comment #7 from Andreas Schwab --- I think it would still be worthwhile to avoid the antipattern (v == c1 && v == c2).

[Bug target/104901] gcc/config/rs6000/mm_malloc.h:46: incorrectLogicOperator

2022-03-21 Thread segher at gcc dot gnu.org via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104901 Segher Boessenkool changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug target/104901] gcc/config/rs6000/mm_malloc.h:46: incorrectLogicOperator

2022-03-21 Thread pc at gcc dot gnu.org via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104901 pc at gcc dot gnu.org changed: What|Removed |Added CC||pc at gcc dot gnu.org --- Commen

[Bug target/104901] gcc/config/rs6000/mm_malloc.h:46: incorrectLogicOperator

2022-03-18 Thread segher at gcc dot gnu.org via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104901 Segher Boessenkool changed: What|Removed |Added CC||segher at gcc dot gnu.org --- Comm

[Bug target/104901] gcc/config/rs6000/mm_malloc.h:46: incorrectLogicOperator

2022-03-14 Thread rguenth at gcc dot gnu.org via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104901 --- Comment #3 from Richard Biener --- It's a way to say a == b == c, no? Not sure if that was intended of course, but it seems so since we follow with if (__alignment < __vec_align) __alignment = __vec_align;