[Bug c++/108927] New: error: too few arguments to function 'long unsigned int __riscv_vsetvlmax_e8mf8(void)'

2023-02-24 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108927 Bug ID: 108927 Summary: error: too few arguments to function 'long unsigned int __riscv_vsetvlmax_e8mf8(void)' Product: gcc Version: 13.0 Status: UNCONFIRMED S

[Bug c++/108967] New: internal compiler error: in expand_debug_expr, at cfgexpand.cc:5450

2023-02-28 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108967 Bug ID: 108967 Summary: internal compiler error: in expand_debug_expr, at cfgexpand.cc:5450 Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal

[Bug c/109082] New: emmintrin.h:1624:16: error: argument 3 must be a literal between 0 and 15, inclusive

2023-03-09 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109082 Bug ID: 109082 Summary: emmintrin.h:1624:16: error: argument 3 must be a literal between 0 and 15, inclusive Product: gcc Version: 13.0 Status: UNCONFIRMED Sev

[Bug c/109082] emmintrin.h:1624:16: error: argument 3 must be a literal between 0 and 15, inclusive

2023-03-09 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109082 --- Comment #1 from Mathieu Malaterre --- Looks like a typo: % head -1624 /usr/lib/gcc-snapshot/lib/gcc/powerpc64le-linux-gnu/13/include/emmintrin.h | tail __v16qu __result; const __v16qu __zeros = { 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0

[Bug target/106322] i386: Wrong code at O2 level (O0 / O1 are working)

2022-08-03 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106322 --- Comment #11 from Mathieu Malaterre --- (In reply to Uroš Bizjak from comment #10) > The reason the test fails with gcc-12 is that gcc-12 enabled > auto-vectorisation for -O2. I can make the symptoms go away by doing: `-O2 -fno-tree-vectoriz

[Bug tree-optimization/106322] 32bits / tree-vectorize: Wrong code at O2 level (-fno-tree-vectorize is working)

2022-08-03 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106322 --- Comment #12 from Mathieu Malaterre --- Created attachment 53406 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53406&action=edit main function with no-tree-optimize attribute

[Bug tree-optimization/106322] 32bits / tree-vectorize: Wrong code at O2 level (-fno-tree-vectorize is working)

2022-08-03 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106322 --- Comment #13 from Mathieu Malaterre --- Created attachment 53407 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53407&action=edit main function with no-tree-optimize attribute

[Bug tree-optimization/106322] 32bits / tree-vectorize: Wrong code at O2 level (-fno-tree-vectorize is working)

2022-08-03 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106322 --- Comment #14 from Mathieu Malaterre --- I can make the symptom go away with a single function attribute: ``` % diff -u * --- /tmp/ii/mul_test.cc.ii.bad 2022-08-03 12:29:41.192263306 + +++ /tmp/ii/mul_test.cc.ii.good 2022-08-03 12:29:41.

[Bug tree-optimization/106322] tree-vectorize: Wrong code at O2 level (-fno-tree-vectorize is working)

2022-08-05 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106322 --- Comment #15 from Mathieu Malaterre --- (In reply to Mathieu Malaterre from comment #11) > (In reply to Uroš Bizjak from comment #10) > > The reason the test fails with gcc-12 is that gcc-12 enabled > > auto-vectorisation for -O2. > > I can

[Bug tree-optimization/106322] tree-vectorize: Wrong code at O2 level (-fno-tree-vectorize is working)

2022-08-08 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106322 --- Comment #16 from Mathieu Malaterre --- Simplified version: % cat demo.cc #include "hwy/highway.h" #include "hwy/tests/test_util-inl.h" struct TestMulHigh { template void operator()(T /*unused*/, D d) { const size_t N = 2; hwy

[Bug tree-optimization/106322] tree-vectorize: Wrong code at O2 level (-fno-tree-vectorize is working)

2022-08-08 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106322 --- Comment #17 from Mathieu Malaterre --- Created attachment 53424 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53424&action=edit g++ -save-temps -O2 -o demo demo.cc -lhwy -lhwy_test

[Bug tree-optimization/106322] tree-vectorize: Wrong code at O2 level (-fno-tree-vectorize is working)

2022-08-08 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106322 --- Comment #18 from Mathieu Malaterre --- Brushed-up example (with Makefile): % more Makefile bytes.cc demo.cc :: Makefile :: CXXFLAGS := -O2 demo: demo.o bytes.o $(CXX) $(CXXFLAGS) -o $@ $^ -lhwy clean:

[Bug tree-optimization/106322] tree-vectorize: Wrong code at O2 level (-fno-tree-vectorize is working)

2022-08-09 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106322 --- Comment #19 from Mathieu Malaterre --- Without hwy dependency: % more Makefile bytes.cc demo.cc :: Makefile :: CXXFLAGS := -O2 demo: demo.o bytes.o $(CXX) $(CXXFLAGS) -o $@ $^ clean: rm -f bytes.o

[Bug tree-optimization/106322] tree-vectorize: Wrong code at O2 level (-fno-tree-vectorize is working)

2022-08-09 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106322 --- Comment #21 from Mathieu Malaterre --- (In reply to Martin Liška from comment #20) > Hmm, can't reproduce with x86_64 compiler with -m32: > > $ g++ --version > g++ (SUSE Linux) 12.1.1 20220721 [revision > 4f15d2234608e82159d030dadb17af678cf

[Bug tree-optimization/106322] tree-vectorize: Wrong code at O2 level (-fno-tree-vectorize is working)

2022-08-09 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106322 --- Comment #23 from Mathieu Malaterre --- Nevermind; I can reproduce the issue with a sid/amd64 chroot: stable64 % schroot -c sid64 sid64 % g++ --version g++ (Debian 12.1.0-7) 12.1.0 Copyright (C) 2022 Free Software Foundation, Inc. This is fr

[Bug tree-optimization/106322] tree-vectorize: Wrong code at O2 level (-fno-tree-vectorize is working)

2022-08-09 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106322 --- Comment #25 from Mathieu Malaterre --- (In reply to Martin Liška from comment #24) > > sid64 % g++ *.cc -O2 -m32 && ./a.out > > Please provide output with --verbose. % g++ --verbose *.cc -O2 -m32 && ./a.out Using built-in specs. COLLECT_G

[Bug tree-optimization/106322] [12/13 Regression] tree-vectorize: Wrong code at O2 level (-fno-tree-vectorize is working) since r12-2404-ga1d27560770818c5

2022-08-09 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106322 --- Comment #30 from Mathieu Malaterre --- (In reply to Martin Liška from comment #29) > (In reply to Kewen Lin from comment #28) > > Sorry for the breakage, I'll have a look tomorrow. > > > > btw, is it able to reproduce the issue on ppc64 (or

[Bug tree-optimization/106322] [12/13 Regression] tree-vectorize: Wrong code at O2 level (-fno-tree-vectorize is working) since r12-2404-ga1d27560770818c5

2022-08-09 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106322 --- Comment #31 from Mathieu Malaterre --- (In reply to Mathieu Malaterre from comment #30) > (In reply to Martin Liška from comment #29) > > (In reply to Kewen Lin from comment #28) > > > Sorry for the breakage, I'll have a look tomorrow. > > >

[Bug tree-optimization/106322] [12/13 Regression] tree-vectorize: Wrong code at O2 level (-fno-tree-vectorize is working) since r12-2404-ga1d27560770818c5

2022-08-09 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106322 --- Comment #33 from Mathieu Malaterre --- (In reply to Kewen Lin from comment #32) > (In reply to Mathieu Malaterre from comment #30) > > (In reply to Martin Liška from comment #29) > > > (In reply to Kewen Lin from comment #28) > > > > Sorry f

[Bug tree-optimization/106322] [12/13 Regression] tree-vectorize: Wrong code at O2 level (-fno-tree-vectorize is working) since r12-2404-ga1d27560770818c5

2022-08-09 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106322 --- Comment #34 from Mathieu Malaterre --- (In reply to Mathieu Malaterre from comment #33) > (In reply to Kewen Lin from comment #32) > > (In reply to Mathieu Malaterre from comment #30) > > > (In reply to Martin Liška from comment #29) > > > >

[Bug tree-optimization/106322] [12/13 Regression] tree-vectorize: Wrong code at O2 level (-fno-tree-vectorize is working) since r12-2404-ga1d27560770818c5

2022-08-09 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106322 --- Comment #35 from Mathieu Malaterre --- (In reply to Mathieu Malaterre from comment #33) > (In reply to Kewen Lin from comment #32) > > (In reply to Mathieu Malaterre from comment #30) > > > (In reply to Martin Liška from comment #29) > > > >

[Bug rtl-optimization/106187] armhf: Miscompilation at O2 level (O0 / O1 are working)

2022-08-10 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106187 --- Comment #51 from Mathieu Malaterre --- (In reply to Richard Earnshaw from comment #50) > Fixed on master so far. Not clear how this is possible. I reported an issue against gcc-11 which could not be reproduced using gcc-12. Are you saying t

[Bug libstdc++/103629] [11/12/13 Regression] Possible miscompilation visible using pthread + exception

2022-08-22 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103629 Mathieu Malaterre changed: What|Removed |Added Known to fail||12.1.0 --- Comment #21 from Mathieu

[Bug libstdc++/103629] [11/12/13 Regression] Possible miscompilation visible using pthread + exception

2022-08-24 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103629 --- Comment #22 from Mathieu Malaterre --- Created attachment 53501 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53501&action=edit working save-temps

[Bug libstdc++/103629] [11/12/13 Regression] Possible miscompilation visible using pthread + exception

2022-08-24 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103629 --- Comment #23 from Mathieu Malaterre --- Created attachment 53502 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53502&action=edit non-working save-temps

[Bug libstdc++/103629] [11/12/13 Regression] Possible miscompilation visible using pthread + exception

2022-08-24 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103629 --- Comment #24 from Mathieu Malaterre --- I have change the openvdb.cc code into: % cat openvdb.cc #include "Tree.h" static std::string do_segfault() { return Tree::treeType(); } #ifdef VIS __attribute__((visibility("default"))) #endif void

[Bug libstdc++/103629] [11/12/13 Regression] wrong-code when mixing mutex with visibility=hidden

2022-08-24 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103629 --- Comment #25 from Mathieu Malaterre --- Looks like there is an easy fix (work-around?): % cat Tree.h #pragma once #include #include class #ifdef VIS __attribute__((visibility("default"))) #endif Tree { public: static const std::string

[Bug libstdc++/103629] [11/12/13 Regression] wrong-code when mixing mutex with visibility=hidden

2022-08-24 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103629 --- Comment #26 from Mathieu Malaterre --- This may be related to: * https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62280

[Bug rtl-optimization/106187] armhf: Miscompilation at O2 level (O0 / O1 are working)

2022-09-02 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106187 --- Comment #53 from Mathieu Malaterre --- For later reference, the gcc-11 symptoms disapear in upstream git after commit: * https://github.com/google/highway/commit/4fa872a2a0d9944cb5fe761669ac63096607d3a3 gcc-12 seems to be generating wrong-

[Bug rtl-optimization/106041] [12/13 Regression] infinite loop in fast_dce at -O1 with aarch64

2022-09-05 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106041 --- Comment #9 from Mathieu Malaterre --- (In reply to Andrew Pinski from comment #3) > If I get some time next weekend I might reduce this further to understand it. > There are only 38 BBs in this function too and they are not large either. Se

[Bug tree-optimization/106322] [12 Regression] tree-vectorize: Wrong code at O2 level (-fno-tree-vectorize is working) since r12-2404-ga1d27560770818c5

2022-09-27 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106322 Mathieu Malaterre changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED

[Bug tree-optimization/106322] [12 Regression] tree-vectorize: Wrong code at O2 level (-fno-tree-vectorize is working) since r12-2404-ga1d27560770818c5

2022-09-27 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106322 --- Comment #52 from Mathieu Malaterre --- For comparison, gcc-snapshot taken from trunk is working as expected: * https://packages.qa.debian.org/g/gcc-snapshot/news/20220920T113715Z.html % /usr/lib/gcc-snapshot/bin/cc -v -O2 -mtune=generic -m

[Bug rtl-optimization/106187] armhf: Miscompilation at O2 level (O0 / O1 are working)

2022-09-27 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106187 --- Comment #57 from Mathieu Malaterre --- (In reply to Richard Earnshaw from comment #55) > (In reply to Mathieu Malaterre from comment #53) > > > > > gcc-12 seems to be generating wrong-code for a different unit-test: > > I've just pushed m

[Bug tree-optimization/106322] [12 Regression] tree-vectorize: Wrong code at O2 level (-fno-tree-vectorize is working) since r12-2404-ga1d27560770818c5

2022-09-27 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106322 Mathieu Malaterre changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED

[Bug c++/107128] New: armhf: floatn-common.h:214:9: error: multiple types in one declaration

2022-10-03 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107128 Bug ID: 107128 Summary: armhf: floatn-common.h:214:9: error: multiple types in one declaration Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal

[Bug c++/107128] armhf: floatn-common.h:214:9: error: multiple types in one declaration

2022-10-03 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107128 --- Comment #2 from Mathieu Malaterre --- > Gcc 13 requires some (older) glibc headers to be fixed up . I could not reproduce it under my Debian amd64/chroot. I'll check with doko@d.o then. Sorry for the noise.

[Bug c++/107128] armhf: floatn-common.h:214:9: error: multiple types in one declaration

2022-10-03 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107128 --- Comment #3 from Mathieu Malaterre --- > some (older) glibc By older what do you mean exactly ? It seems my system provides glibc 2.35: malat@amdahl /tmp % apt-cache policy libc6-dev libc6-dev: Installed: 2.35-1 Candidate: 2.35-1 Vers

[Bug c++/108081] New: -O0 leads to R_MIPS_TLS_GD error

2022-12-13 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108081 Bug ID: 108081 Summary: -O0 leads to R_MIPS_TLS_GD error Product: gcc Version: 12.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++

[Bug target/108081] -O0 leads to R_MIPS_TLS_GD error

2022-12-13 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108081 Mathieu Malaterre changed: What|Removed |Added Resolution|WONTFIX |--- Status|RESOLVED

[Bug target/108081] -O0 leads to R_MIPS_TLS_GD error

2022-12-13 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108081 --- Comment #3 from Mathieu Malaterre --- > 11956#c6 > [...] > -mxgot might help, Pay attention that my bug report is about `R_MIPS_TLS_GD` and not `R_MIPS_CALL16` which indeed can be fixed by `-mxgot`

[Bug target/106187] armhf: Miscompilation at O2 level (O0 / O1 are working)

2022-07-08 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106187 --- Comment #16 from Mathieu Malaterre --- This is one is producing wrong code: % gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/arm-linux-gnueabihf/11/lto-wrapper Target: arm-linux-gnueabihf Configured with: ../s

[Bug target/106187] armhf: Miscompilation at O2 level (O0 / O1 are working)

2022-07-08 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106187 --- Comment #18 from Mathieu Malaterre --- The complete line to generate the *.ii file is: ``` % /usr/bin/g++ -DHWY_STATIC_DEFINE -I/home/malat/highway -O2 -fstrict-aliasing -ggdb3 -fPIE -fvisibility=hidden -fvisibility-inlines-hidden -Wno-buil

[Bug target/106187] armhf: Miscompilation at O2 level (O0 / O1 are working)

2022-07-08 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106187 --- Comment #20 from Mathieu Malaterre --- The Debian package highway 0.17.0-9 is not build with neon option (aka ARM7=OFF in cmake), the code build just fine and test suite run fine (-O1): * https://buildd.debian.org/status/fetch.php?pkg=highw

[Bug c++/106322] New: i386: Wrong code at O2 level (O0 / O1 are working)

2022-07-16 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106322 Bug ID: 106322 Summary: i386: Wrong code at O2 level (O0 / O1 are working) Product: gcc Version: 12.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Compon

[Bug c++/106322] i386: Wrong code at O2 level (O0 / O1 are working)

2022-07-16 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106322 --- Comment #1 from Mathieu Malaterre --- I can reduce the gtest code to simply: ``` HWY_NOINLINE void TestAllMulHigh() { ForPartialVectors test; test(int16_t()); // test(uint16_t()); } ```

[Bug c++/106322] i386: Wrong code at O2 level (O0 / O1 are working)

2022-07-16 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106322 Mathieu Malaterre changed: What|Removed |Added CC||malat at debian dot org --- Comment

[Bug c++/106322] i386: Wrong code at O2 level (O0 / O1 are working)

2022-07-16 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106322 --- Comment #3 from Mathieu Malaterre --- Created attachment 53306 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53306&action=edit gcc-12 -O2 -save-temps

[Bug c++/106322] i386: Wrong code at O2 level (O0 / O1 are working)

2022-07-16 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106322 --- Comment #4 from Mathieu Malaterre --- gcc-11 version on my side is: % gcc-11 --version gcc-11 (Debian 11.3.0-4) 11.3.0 Copyright (C) 2021 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There i

[Bug c++/106322] i386: Wrong code at O2 level (O0 / O1 are working)

2022-07-16 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106322 --- Comment #5 from Mathieu Malaterre --- Compilation line for -save-temps is: % /usr/bin/g++-12 -DHWY_STATIC_DEFINE -I"/home/malat/highway-0.17.1~git20220711.f0a396a" -O2 -fPIE -fvisibility=hidden -fvisibility-inlines-hidden -Wno-builtin-macro

[Bug c++/106322] i386: Wrong code at O2 level (O0 / O1 are working)

2022-07-16 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106322 --- Comment #6 from Mathieu Malaterre --- Using `-fno-strict-aliasing` causes the same symptoms: /usr/bin/g++-12 -DHWY_STATIC_DEFINE -I"/home/malat/highway-0.17.1~git20220711.f0a396a" -O2 -fno-strict-aliasing -fPIE -fvisibility=hidden -fvisibil

[Bug c++/106322] i386: Wrong code at O2 level (O0 / O1 are working)

2022-07-16 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106322 --- Comment #7 from Mathieu Malaterre --- I can make it fails with sanitize=address: /usr/bin/g++-12 -DHWY_STATIC_DEFINE -I"/home/malat/highway-0.17.1~git20220711.f0a396a" -O2 -fsanitize=address -fPIE -fvisibility=hidden -fvisibility-inlines-hi

[Bug target/106322] i386: Wrong code at O2 level (O0 / O1 are working)

2022-07-18 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106322 --- Comment #9 from Mathieu Malaterre --- (In reply to Andrew Pinski from comment #8) > Does -fwrapv fix the issue? No. This seems like the exact same symptoms: % ./tests/mul_test "--gtest_filter=HwyMulTestGroup/HwyMulTest.TestAllMulHigh/Emu12

[Bug c++/110804] [13 regression] eliminate_stmt ICE on aarch64

2023-07-25 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110804 Mathieu Malaterre changed: What|Removed |Added CC||malat at debian dot org --- Comment

[Bug target/111212] New: internal compiler error: in extract_insn, at recog.cc:2791

2023-08-28 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111212 Bug ID: 111212 Summary: internal compiler error: in extract_insn, at recog.cc:2791 Product: gcc Version: 13.2.0 Status: UNCONFIRMED Severity: normal

[Bug target/111212] internal compiler error: in extract_insn, at recog.cc:2791

2023-08-28 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111212 --- Comment #1 from Mathieu Malaterre --- Compilation line: % /usr/bin/c++ -freport-bug -DHWY_STATIC_DEFINE -DTOOLCHAIN_MISS_ASM_HWCAP_H -I/home/malat/highway -maltivec -mcpu=power8 -O2 -g -DNDEBUG -fPIE -fvisibility=hidden -fvisibility-inline

[Bug target/111212] [13/14 Regression] internal compiler error: in extract_insn, at recog.cc:2791

2023-08-28 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111212 --- Comment #2 from Mathieu Malaterre --- reduced: % g++ -maltivec -mcpu=power8 -O2 -c testcase.i testcase.i:15:30: warning: '{anonymous}::m {anonymous}::n(a) [with f = short int]' used but never defined 15 | template m n(a); |

[Bug target/111231] New: armhf: Miscompilation at O2 level

2023-08-29 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111231 Bug ID: 111231 Summary: armhf: Miscompilation at O2 level Product: gcc Version: 13.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target

[Bug target/111231] armhf: Miscompilation at O2 level

2023-08-29 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111231 --- Comment #1 from Mathieu Malaterre --- Created attachment 55816 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55816&action=edit Preprocessed source % /usr/bin/c++ -save-temps -DHWY_STATIC_DEFINE -I/home/malat/highway -O2 -g -DNDEBUG -

[Bug target/111231] armhf: Miscompilation at O2 level

2023-08-29 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111231 --- Comment #2 from Mathieu Malaterre --- reported upstream as: * https://github.com/google/highway/issues/1683

[Bug target/111231] armhf: Miscompilation at O2 level (O1 is working)

2023-08-30 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111231 --- Comment #3 from Mathieu Malaterre --- creduce process started on amhdal.d.o machine: % creduce check.sh mul_test.cc ===< 1797132 >=== running 3 interestingness tests in parallel ===< pass_unifdef :: 0 >=== (10.0 %, 31474 bytes) [...] will

[Bug target/111231] armhf: Miscompilation at O2 level (O1 is working)

2023-08-30 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111231 --- Comment #4 from Mathieu Malaterre --- Intermediate result (creduce Debian/sid): #include "hwy/tests/test_util-inl.h" namespace hwy { namespace HWY_NAMESPACE { struct a { template void operator()(b, c d) { using e = MakeUnsigned;

[Bug target/111268] New: internal compiler error: in to_constant, at poly-int.h:504

2023-09-01 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111268 Bug ID: 111268 Summary: internal compiler error: in to_constant, at poly-int.h:504 Product: gcc Version: 13.2.0 Status: UNCONFIRMED Severity: normal

[Bug target/111268] internal compiler error: in to_constant, at poly-int.h:504

2023-09-01 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111268 --- Comment #2 from Mathieu Malaterre --- % /usr/lib/gcc-snapshot/bin/g++ --version g++ (Debian 20230811-1) 14.0.0 20230811 (experimental) [master r14-3139-g68783211f66] Copyright (C) 2023 Free Software Foundation, Inc. This is free software; se

[Bug target/111268] internal compiler error: in to_constant, at poly-int.h:504

2023-09-01 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111268 --- Comment #1 from Mathieu Malaterre --- Created attachment 55830 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55830&action=edit preprocessed source % /usr/lib/gcc-snapshot/bin/g++ -O2 -g -DNDEBUG -c testcase.i

[Bug target/111268] internal compiler error: in to_constant, at poly-int.h:504

2023-09-01 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111268 --- Comment #3 from Mathieu Malaterre --- For reference % /usr/lib/gcc-snapshot/bin/gcc -march=armv8.2-a+sve -O2 -c m.c && echo "success" success with % cat m.c #pragma GCC aarch64 "arm_sve.h" svbool_t foo (svint8_t a, svint8_t b, svbool_t c

[Bug tree-optimization/111268] [14 Regression] internal compiler error: in to_constant, at poly-int.h:504

2023-09-05 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111268 --- Comment #5 from Mathieu Malaterre --- (In reply to Andrew Pinski from comment #4) > Looks like this one is already fixed. Same symptoms with 20230902 snapshot: * https://buildd.debian.org/status/fetch.php?pkg=highway&arch=arm64&ver=1.0.8%7

[Bug target/111231] armhf: Miscompilation at O2 level (O1 is working)

2023-09-05 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111231 --- Comment #5 from Mathieu Malaterre --- Result from cvise (+manual editing): c++ -Wfatal-errors -Wall -Wextra -Werror -o works -O1 -march=armv7-a -mfpu=neon-vfpv4 -mfloat-abi=hard -mfp16-format=ieee step7.cc -> exit(0) c++ -Wfatal-errors -Wa

[Bug target/110643] [13/14 Regression] aarch64: Miscompilation at O1 level (O0 is working)

2023-09-05 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110643 --- Comment #12 from Mathieu Malaterre --- regression started today % cvise check.sh math_test.cc 00:00:27 INFO ===< 3971165 >=== 00:00:27 INFO running 4 interestingness tests in parallel 00:00:27 INFO INITIAL PAS

[Bug target/111051] [14 Regression] highway-1.0.6 fails to build as gcc-14.0.0/lib/gcc/x86_64-unknown-linux-gnu/14.0.0/include/avxintrin.h:1238:1: error: inlining failed in call to 'always_inline' '__

2023-09-08 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111051 Mathieu Malaterre changed: What|Removed |Added CC||malat at debian dot org --- Comment

[Bug target/110960] TestSatWidenMulPairwiseAdd in the Google Highway test suite fails when compiled with GCC 12 or later with the -mcpu=power9 option

2023-09-08 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110960 --- Comment #7 from Mathieu Malaterre --- @rguenth You added `needs-bisection` keyword, but the example is quite small: 154 lines of code.

[Bug target/111366] New: error: inlining failed in call to 'always_inline' 'hwy::PreventElision(int&)void': target specific option mismatch

2023-09-11 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111366 Bug ID: 111366 Summary: error: inlining failed in call to 'always_inline' 'hwy::PreventElision(int&)void': target specific option mismatch Product: gcc Version:

[Bug target/111366] error: inlining failed in call to 'always_inline' 'hwy::PreventElision(int&)void': target specific option mismatch

2023-09-11 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111366 --- Comment #1 from Mathieu Malaterre --- Full log: * https://launchpadlibrarian.net/684588621/buildlog_ubuntu-mantic-ppc64el.highway_1.0.7-1_BUILDING.txt.gz

[Bug target/111366] error: inlining failed in call to 'always_inline' 'hwy::PreventElision(int&)void': target specific option mismatch

2023-09-11 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111366 --- Comment #2 from Mathieu Malaterre --- Typical setup: * https://gcc.godbolt.org/z/5W45a6j8x

[Bug target/111366] error: inlining failed in call to 'always_inline' 'hwy::PreventElision(int&)void': target specific option mismatch

2023-09-11 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111366 --- Comment #3 from Mathieu Malaterre --- compilation flags required are: `-O1 -mcpu=power9 -flto=auto`

[Bug target/111366] error: inlining failed in call to 'always_inline' 'hwy::PreventElision(int&)void': target specific option mismatch

2023-09-11 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111366 --- Comment #4 from Mathieu Malaterre --- reduction started: % cvise check.sh skeleton_test.cc 00:00:02 INFO ===< 4165591 >=== 00:00:02 INFO running 4 interestingness tests in parallel 00:00:02 INFO INITIAL PASSES

[Bug target/111367] New: Error: operand out of range (0x1391c is not between 0xffffffffffff8000 and 0x7fff)

2023-09-11 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111367 Bug ID: 111367 Summary: Error: operand out of range (0x1391c is not between 0x8000 and 0x7fff) Product: gcc Version: 14.0 Status: UNCONFIRMED Sever

[Bug target/111367] Error: operand out of range (0x1391c is not between 0xffffffffffff8000 and 0x7fff)

2023-09-11 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111367 --- Comment #1 from Mathieu Malaterre --- full log: https://buildd.debian.org/status/fetch.php?pkg=highway&arch=powerpc&ver=1.0.8%7Egit20230830.fed142a-1&stamp=1694162297&raw=0

[Bug target/111367] Error: operand out of range (0x1391c is not between 0xffffffffffff8000 and 0x7fff)

2023-09-11 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111367 --- Comment #2 from Mathieu Malaterre --- I am using gcc-snapshot from Debian/sid package. It does contains fixes from PR/111212.

[Bug target/111367] Error: operand out of range (0x1391c is not between 0xffffffffffff8000 and 0x7fff)

2023-09-11 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111367 --- Comment #3 from Mathieu Malaterre --- Reduced test case: % cat bench_sort.cc #define HWY_PRAGMA(tokens) _Pragma(#tokens) #define HWY_PUSH_ATTRIBUTES(targets_str) HWY_PRAGMA(GCC target targets_str) #define HWY_BEFORE_NAMESPACE() HWY_PUSH_ATT

[Bug target/111366] error: inlining failed in call to 'always_inline' 'hwy::PreventElision(int&)void': target specific option mismatch

2023-09-11 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111366 --- Comment #7 from Mathieu Malaterre --- In case this helps resolve this, here is the cvise-reduced code: % cat skeleton_test.cc #include #define HWY_PRAGMA(tokens) _Pragma(#tokens) namespace hwy { #define HWY_PUSH_ATTRIBUTES(targets_str) HWY

[Bug target/111366] error: inlining failed in call to 'always_inline' 'hwy::PreventElision(int&)void': target specific option mismatch

2023-09-11 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111366 --- Comment #8 from Mathieu Malaterre --- Further reduced: #include #define HWY_PRAGMA(tokens) _Pragma(#tokens) #define HWY_PUSH_ATTRIBUTES(targets_str) HWY_PRAGMA(GCC target targets_str) __attribute__((always_inline)) void PreventElision() {

[Bug target/111366] error: inlining failed in call to 'always_inline' 'hwy::PreventElision(int&)void': target specific option mismatch

2023-09-11 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111366 --- Comment #11 from Mathieu Malaterre --- (In reply to Kewen Lin from comment #9) > It looks to me that the error message is expected, because the source code > forces the function as always_inline, users would like it to be inlined > always, i

[Bug target/111386] New: flto=auto => lto1: fatal error: target specific builtin not available

2023-09-12 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111386 Bug ID: 111386 Summary: flto=auto => lto1: fatal error: target specific builtin not available Product: gcc Version: 13.2.0 Status: UNCONFIRMED Severity: normal

[Bug target/111386] flto=auto => lto1: fatal error: target specific builtin not available

2023-09-12 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111386 Mathieu Malaterre changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug target/111231] [13/14 Regression] armhf: Miscompilation at O2 level (O1 is working)

2023-09-14 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111231 --- Comment #6 from Mathieu Malaterre --- Code in #c4 and #c5 are bogus. They also fails with g++-12. Let me start my cvise machinery over again (may take some time).

[Bug target/111366] error: inlining failed in call to 'always_inline' 'hwy::PreventElision(int&)void': target specific option mismatch

2023-09-14 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111366 --- Comment #15 from Mathieu Malaterre --- For some reason the no-htm flag does not seems to work in my case: % /usr/bin/c++ -O1 -mcpu=power8 -flto=auto -c skeleton_test.cc skeleton_test.cc: In member function 'TestFloorLog2::operator() >(int,

[Bug target/111366] error: inlining failed in call to 'always_inline' 'hwy::PreventElision(int&)void': target specific option mismatch

2023-09-14 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111366 --- Comment #16 from Mathieu Malaterre --- Interesting, the following works for me: % /usr/bin/c++ -O1 -mcpu=power8 -mno-htm -flto=auto -c skeleton_test.cc

[Bug target/111231] armhf: Miscompilation with -O2/-fno-exceptions level (-O2 is working)

2023-09-15 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111231 --- Comment #7 from Mathieu Malaterre --- new cvise setup started today: % cvise check.sh widen_mul_test.cc 00:01:16 INFO ===< 1427429 >=== 00:01:16 INFO running 4 interestingness tests in parallel 00:01:16 INFO INITIAL PASSES 00:01:16 INFO ===

[Bug target/110622] x86: Miscompilation at O1 level (O0 is working)

2023-09-21 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110622 Mathieu Malaterre changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED

[Bug target/110622] x87: Miscompilation at O2 level (O1 is working)

2023-09-21 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110622 --- Comment #10 from Mathieu Malaterre --- Created attachment 55959 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55959&action=edit cvise reduced test case

[Bug target/110622] x87: Miscompilation at O2 level (O1 is working)

2023-09-21 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110622 --- Comment #11 from Mathieu Malaterre --- Typical setup: g++ -fno-asynchronous-unwind-tables -fno-exceptions -fno-rtti -DHIDESYMPTOM -std=c++11 -g -m32 -fexcess-precision=fast -O2 -o works math_test.cc -Wfatal-errors -Wall -Wextra -Wpedantic -

[Bug target/110622] x87: Miscompilation at O2 level (O1 is working)

2023-09-21 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110622 --- Comment #12 from Mathieu Malaterre --- I am seeing a difference in result (log1p computation) in the range: 4318952042648305665 - 0x1.1p-64 4368493837572636672 - 0x1.002p-53 the other values seems to match expectation of log1p

[Bug target/110622] x87: Miscompilation at O2 level (O1 is working)

2023-09-21 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110622 --- Comment #14 from Mathieu Malaterre --- (In reply to Andrew Pinski from comment #13) > (In reply to Mathieu Malaterre from comment #12) > > I am seeing a difference in result (log1p computation) in the range: > > > > 4318952042648305665 - 0x

[Bug target/110622] x87: Miscompilation at O2 level (O1 is working)

2023-09-21 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110622 --- Comment #16 from Mathieu Malaterre --- (In reply to Xi Ruoyao from comment #15) > (In reply to Mathieu Malaterre from comment #14) > > (In reply to Andrew Pinski from comment #13) > > > (In reply to Mathieu Malaterre from comment #12) > > >

[Bug target/111522] New: Different code path for static initialization with flto

2023-09-21 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111522 Bug ID: 111522 Summary: Different code path for static initialization with flto Product: gcc Version: 13.2.0 Status: UNCONFIRMED Severity: normal Pri

[Bug target/111522] Different code path for static initialization with flto

2023-09-25 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111522 --- Comment #2 from Mathieu Malaterre --- (In reply to Andrew Pinski from comment #1) > I think this is just broken code. > > It does: > #define HWY_BEFORE_NAMESPACE() > \ > HWY_PUSH_ATTRIBUTES("a

[Bug target/111522] Different code path for static initialization with flto

2023-09-25 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111522 --- Comment #3 from Mathieu Malaterre --- For reference: * https://github.com/google/highway/commit/fea3dba9cfec3a74ddcd8ecac3a5d4d8429191e4

[Bug target/111522] Different code path for static initialization with flto

2023-09-25 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111522 --- Comment #4 from Mathieu Malaterre --- > So the original > (upstream) code is somewhat buggy as it rely on lazy init for global var. Those global vars are in different namespace, I actually fail to underwhat why the definition with ",cpu=pow

[Bug target/111522] Different code path for static initialization with flto

2023-09-25 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111522 --- Comment #6 from Mathieu Malaterre --- (In reply to Andrew Pinski from comment #5) > (In reply to Mathieu Malaterre from comment #4) > > > So the original > > > (upstream) code is somewhat buggy as it rely on lazy init for global var. > > >

[Bug target/111522] Different code path for static initialization with flto

2023-09-25 Thread malat at debian dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111522 --- Comment #7 from Mathieu Malaterre --- Created attachment 55987 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55987&action=edit gcc -E -P

  1   2   >