[Bug c/107826] New: ice during GIMPLE pass: slp

2022-11-22 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107826 Bug ID: 107826 Summary: ice during GIMPLE pass: slp Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c

[Bug middle-end/107734] [13 Regression] valgrind error for gcc/testsuite/cc.target/i386/pr46051.c

2022-11-17 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107734 --- Comment #10 from David Binderman --- (In reply to Andrew Pinski from comment #9) > Fixed. Thanks for that. Would it ok to manually check all uses of sbitmap, to make sure they initialise bits appropriately, or would it be better to

[Bug c++/86426] g++ ICE at on valid code in tree_operand_check, at tree.h:3615

2023-01-16 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86426 --- Comment #11 from David Binderman --- Probably still broken. One for Jason ?

[Bug tree-optimization/108523] -O1 -fcode-hoisting causes long compilation time ?

2023-01-24 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108523 --- Comment #4 from David Binderman --- Seems to run fine in about 0.1 seconds with g:4d08c674b0114622, dated 20221129. That seems to be about 533 commits. I'll have a go at a git bisect.

[Bug c/108523] New: -O1 -fcode-hoisting causes long compilation time ?

2023-01-24 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108523 Bug ID: 108523 Summary: -O1 -fcode-hoisting causes long compilation time ? Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug tree-optimization/108523] -O1 -fcode-hoisting causes long compilation time ?

2023-01-24 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108523 --- Comment #3 from David Binderman --- Problem seems to start sometime before git hash g:9b111debbfb79a0a, dated 20221229. I'll try a build of a month earlier.

[Bug tree-optimization/108523] -O1 -fcode-hoisting causes long compilation time ?

2023-01-24 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108523 --- Comment #1 from David Binderman --- Also won't run to completion with a ulimit of 750 seconds. Trying 1200 seconds.

[Bug tree-optimization/108523] -O1 -fcode-hoisting causes long compilation time ?

2023-01-24 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108523 --- Comment #2 from David Binderman --- Doesn't complete in 1200 seconds.

[Bug tree-optimization/108523] -O1 -fcode-hoisting causes long compilation time ?

2023-01-24 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108523 --- Comment #5 from David Binderman --- Current range seems to be g:4d08c674b0114622 .. g:400d9fc1f0433611 which is 133 commits.

[Bug tree-optimization/108523] -O1 -fcode-hoisting causes long compilation time ?

2023-01-24 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108523 David Binderman changed: What|Removed |Added CC||rguenther at suse dot de --- Comment

[Bug tree-optimization/108523] -O1 -fcode-hoisting causes long compilation time ?

2023-01-24 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108523 --- Comment #6 from David Binderman --- Git range now seems to be g:4d08c674b0114622 .. g:b2aa75ded65f8c02 which is a range of 33 commits.

[Bug tree-optimization/108523] -O1 -fcode-hoisting causes long compilation time ?

2023-01-24 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108523 --- Comment #7 from David Binderman --- Git range now seems to be g:4d08c674b0114622 .. g:36cabc257dfb7dd4 which is 8 commits.

[Bug tree-optimization/108482] [13 Regression] ice in expand_LOOP_DIST_ALIAS with -O3 -ftrivial-auto-var-init=zero

2023-01-21 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108482 David Binderman changed: What|Removed |Added CC||rguenther at suse dot de --- Comment

[Bug tree-optimization/108482] [13 Regression] ice in expand_LOOP_DIST_ALIAS with -O3 -ftrivial-auto-var-init=zero

2023-01-21 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108482 --- Comment #11 from David Binderman --- It looks to me like g:af96500eea72c674a5686b35c66202ef2bd9688f is the culprit. Over to Richard for their best advice.

[Bug tree-optimization/108482] [13 Regression] ice in expand_LOOP_DIST_ALIAS with -O3 -ftrivial-auto-var-init=zero

2023-01-21 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108482 --- Comment #9 from David Binderman --- (In reply to David Binderman from comment #8) > Current range is about 151 revisions. After a few more rounds, current range seems to be g:fbad7a74aaaddea3 to g:c16c40808331a029, some 10 commits.

[Bug tree-optimization/108482] [13 Regression] ice in expand_LOOP_DIST_ALIAS with -O3 -ftrivial-auto-var-init=zero

2023-01-21 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108482 --- Comment #6 from David Binderman --- (In reply to David Binderman from comment #5) > (In reply to David Binderman from comment #0) > > The bug seems to exist since sometime before g:02c031088ac0bbf7, dated > > 20221220. > > I tried out a

[Bug tree-optimization/108482] [13 Regression] ice in expand_LOOP_DIST_ALIAS with -O3 -ftrivial-auto-var-init=zero

2023-01-21 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108482 --- Comment #5 from David Binderman --- (In reply to David Binderman from comment #0) > The bug seems to exist since sometime before g:02c031088ac0bbf7, dated > 20221220. I tried out a revision from a month earlier, dated 2022-11-20,

[Bug tree-optimization/108482] [13 Regression] ice in expand_LOOP_DIST_ALIAS with -O3 -ftrivial-auto-var-init=zero

2023-01-21 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108482 --- Comment #7 from David Binderman --- (In reply to David Binderman from comment #6) > (In reply to David Binderman from comment #5) > > (In reply to David Binderman from comment #0) > > > The bug seems to exist since sometime before

[Bug c/102760] ICE: in decompose, at wide-int.h:984

2023-01-25 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102760 David Binderman changed: What|Removed |Added CC||dcb314 at hotmail dot com ---

[Bug tree-optimization/108523] [13 Regression] -O1 -fcode-hoisting causes long compilation time ?

2023-01-25 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108523 --- Comment #16 from David Binderman --- cvise produces: int g_149, g_167, g_481; main() { int *l_1478 = _149; *l_1478 ^= g_167; lbl_1481: for (;;) { g_481 = 1; for (; g_481; g_481 += 1) { g_167 ^= *l_1478; if (g_149)

[Bug tree-optimization/108523] [13 Regression] -O1 -fcode-hoisting causes long compilation time ?

2023-01-25 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108523 --- Comment #15 from David Binderman --- (In reply to Richard Biener from comment #14) > Fixed, but I'll see if somebody comes up with a reduced testcase. I have a reduction running with cvise.

[Bug c/108547] New: ice in decompose, at wide-int.h:984 for -O2 with -Wall

2023-01-25 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108547 Bug ID: 108547 Summary: ice in decompose, at wide-int.h:984 for -O2 with -Wall Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug c/102760] ICE: in decompose, at wide-int.h:984

2023-01-25 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102760 --- Comment #8 from David Binderman --- (In reply to Andrew Pinski from comment #7) > (In reply to David Binderman from comment #6) > > I see very similar for this legal C code: > > That seems like a different issue, please file it seperately.

[Bug c++/88853] ICE: verify_type failed (error: type variant differs by TYPE_PACKED) with -fpack-struct -g

2023-01-26 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88853 David Binderman changed: What|Removed |Added CC||dcb314 at hotmail dot com --- Comment

[Bug c/108596] New: error: EDGE_CROSSING missing across section boundary

2023-01-30 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108596 Bug ID: 108596 Summary: error: EDGE_CROSSING missing across section boundary Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug tree-optimization/108482] [13 Regression] ice in expand_LOOP_DIST_ALIAS with -O3 -ftrivial-auto-var-init=zero

2023-01-21 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108482 --- Comment #8 from David Binderman --- (In reply to David Binderman from comment #7) > (In reply to David Binderman from comment #6) > > (In reply to David Binderman from comment #5) > > > (In reply to David Binderman from comment #0) > > > >

[Bug c/108482] New: ice in expand_LOOP_DIST_ALIAS, at internal-fn.cc:2737

2023-01-20 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108482 Bug ID: 108482 Summary: ice in expand_LOOP_DIST_ALIAS, at internal-fn.cc:2737 Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug c/108482] ice in expand_LOOP_DIST_ALIAS, at internal-fn.cc:2737

2023-01-20 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108482 --- Comment #1 from David Binderman --- Reduced code seems to be: int g_30, g_261, g_263, func_1___trans_tmp_17; int **g_120; int *g_530; void func_1() { int *l_29 = _30; *l_29 = 1; g_263 = 0; for (; g_263 <= 1; g_263 += 1) { g_530

[Bug c/107609] New: ice in extract_insn, at recog.cc:2791

2022-11-10 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107609 Bug ID: 107609 Summary: ice in extract_insn, at recog.cc:2791 Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c

[Bug c/107510] New: gcc/config/gcn/gcn.cc:4930:9: style: Same expression on both sides of '||'. [duplicateExpression]

2022-11-02 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107510 Bug ID: 107510 Summary: gcc/config/gcn/gcn.cc:4930:9: style: Same expression on both sides of '||'. [duplicateExpression] Product: gcc Version: 13.0 Status: UNCONFIRMED

[Bug c++/107593] New: ice with -Wduplicated-cond

2022-11-09 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107593 Bug ID: 107593 Summary: ice with -Wduplicated-cond Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++

[Bug tree-optimization/107668] [13 Regression] ICE: in clear_nan, at value-range.h:1167 with -fsanitize=float-cast-overflow and _Complex int

2022-11-14 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107668 --- Comment #4 from David Binderman --- (In reply to David Binderman from comment #3) > Trying git revision 2d5c4a16dd833aa0. That looks good. Trying 59a63247992eb131.

[Bug tree-optimization/107668] [13 Regression] ICE: in clear_nan, at value-range.h:1167 with -fsanitize=float-cast-overflow and _Complex int

2022-11-14 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107668 --- Comment #5 from David Binderman --- (In reply to David Binderman from comment #4) > (In reply to David Binderman from comment #3) > > Trying git revision 2d5c4a16dd833aa0. > > That looks good. Trying 59a63247992eb131. Looks bad. Trying

[Bug tree-optimization/107668] [13 Regression] ICE: in clear_nan, at value-range.h:1167 with -fsanitize=float-cast-overflow and _Complex int

2022-11-14 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107668 --- Comment #3 from David Binderman --- Trying git revision 2d5c4a16dd833aa0.

[Bug tree-optimization/107668] [13 Regression] ICE: in clear_nan, at value-range.h:1167 with -fsanitize=float-cast-overflow and _Complex int

2022-11-14 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107668 --- Comment #6 from David Binderman --- (In reply to David Binderman from comment #5) > (In reply to David Binderman from comment #4) > > (In reply to David Binderman from comment #3) > > > Trying git revision 2d5c4a16dd833aa0. > > > > That

[Bug tree-optimization/107668] [13 Regression] ICE: in clear_nan, at value-range.h:1167 with -fsanitize=float-cast-overflow and _Complex int

2022-11-13 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107668 David Binderman changed: What|Removed |Added CC||dcb314 at hotmail dot com ---

[Bug tree-optimization/107668] [13 Regression] ICE: in clear_nan, at value-range.h:1167 with -fsanitize=float-cast-overflow and _Complex int

2022-11-13 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107668 --- Comment #2 from David Binderman --- Reduced C++ code seems to be: --- /home/dcb36/cvise/bug862.cc --- float dot(); float intersectcylinder_md; void intersectcylinder(float ) { float nd = dot(); dist = 0 / nd; float offset =

[Bug rtl-optimization/108596] [10/11/12 Regression] error: EDGE_CROSSING missing across section boundary

2023-02-02 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108596 --- Comment #7 from David Binderman --- (In reply to Jakub Jelinek from comment #6) > Fixed on the trunk so far. linux-6.2-rc6 builds fine, when built with -O3. Thanks for the quick fix.

[Bug middle-end/109031] csmith: possible bad code with -O2 -fno-strict-aliasing

2023-03-08 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109031 --- Comment #9 from David Binderman --- (In reply to Martin Liška from comment #8) > > but then if diff returns 1, the script should return 0 and > > if diff returns 0, then the script should return 1. > > You can take an inspiration here: >

[Bug middle-end/109031] csmith: possible bad code with -O2 -fno-strict-aliasing

2023-03-08 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109031 --- Comment #7 from David Binderman --- (In reply to David Binderman from comment #4) > Created attachment 54596 [details] > C source code > > After 3 hours further reduction. I am struggling with further reduction. My bash knowledge is

[Bug middle-end/109031] csmith: possible bad code with -O2 -fno-strict-aliasing

2023-03-06 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109031 --- Comment #4 from David Binderman --- Created attachment 54596 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54596=edit C source code After 3 hours further reduction.

[Bug middle-end/109031] csmith: possible bad code with -O2 -fno-strict-aliasing

2023-03-06 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109031 --- Comment #3 from David Binderman --- 20220508 is good, so the range is 20220508 to 20220515. In git hash terms, that's g:a1947c92f7cda5f6cf7b8d8a9a44f6dd45352c03 to g:18547874ee205d830acb31f1e3c1c89fc7725c14. I will try to reduce the code

[Bug middle-end/109031] csmith: possible bad code with -O2 -fno-strict-aliasing

2023-03-08 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109031 --- Comment #11 from David Binderman --- (In reply to Martin Liška from comment #10) > What about: > > /usr/bin/gcc -w -Werror=implicit bug892.c -o one.exe > && (./one.exe 1 | fgrep "checksum after hashing g_50 :" > 1) > &&

[Bug middle-end/109031] csmith: possible bad code with -O2 -fno-strict-aliasing

2023-03-08 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109031 --- Comment #18 from David Binderman --- Part way through reduction, the C code seems to be int crc32_tab_0; int crc32_context = 0xUL; void main(int , char []) { { int crc; int i; i = 0; for (; i < 256; i++)

[Bug middle-end/109031] csmith: possible bad code with -O2 -fno-strict-aliasing

2023-03-08 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109031 --- Comment #13 from David Binderman --- (In reply to Martin Liška from comment #12) > > perl program converted to 0 is proving to be a challenge. > > perl? Please provide a complete script reproducer. cvise is written in perl, isn't it ?

[Bug middle-end/109031] csmith: possible bad code with -O2 -fno-strict-aliasing

2023-03-08 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109031 --- Comment #15 from David Binderman --- (In reply to Martin Liška from comment #14) > > cvise is written in perl, isn't it ? You've got my cvise script. > > No, it's written in Python. Of course. How stupid of me. > So show me how you run

[Bug middle-end/109031] csmith: possible bad code with -O2 -fno-strict-aliasing

2023-03-08 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109031 --- Comment #17 from David Binderman --- (In reply to Martin Liška from comment #16) > bash -x qwe.sh bug892.c That's a really useful tip. Thanks. I've debugged the script some more and now have: rm -f 1 2 one.exe two.exe /usr/bin/gcc -w

[Bug c/109087] csmith: end of year runtime bug ?

2023-03-10 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109087 --- Comment #1 from David Binderman --- Git range seems to be g:d0a3d55ae4a2656f .. g:4f1314f547f69d3a, which is about 533 commits. Trying a bisect.

[Bug c/109087] New: csmith: end of year runtime bug ?

2023-03-10 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109087 Bug ID: 109087 Summary: csmith: end of year runtime bug ? Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c

[Bug c/109087] csmith: end of year runtime bug ?

2023-03-10 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109087 --- Comment #2 from David Binderman --- Git range seems to be g:a996888327c2248b .. g:4f1314f547f69d3a, which is 134 commits.

[Bug c/109087] csmith: end of year runtime bug ?

2023-03-10 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109087 --- Comment #4 from David Binderman --- Git range seems to be g:37d8312f560f1e2f .. g:0cb5d7cdbab8e5f8, which is 9 commits. No hot candidate yet.

[Bug c/109087] csmith: end of year runtime bug ?

2023-03-10 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109087 --- Comment #5 from David Binderman --- First bad commit seems to be: eef81eefcdc2a58111e50eb2162ea1f5becc8004 is the first bad commit commit eef81eefcdc2a58111e50eb2162ea1f5becc8004 Author: Jan Hubicka Date: Thu Dec 22 10:55:46 2022 +0100

[Bug c/109087] csmith: end of year runtime bug ?

2023-03-10 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109087 --- Comment #3 from David Binderman --- Git range now seems to be g:a996888327c2248b .. g:0cb5d7cdbab8e5f8, which is 33 commits.

[Bug target/109087] [13 Regression] csmith: end of year runtime bug since r13-4839-geef81eefcdc2a581

2023-03-10 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109087 --- Comment #9 from David Binderman --- (In reply to Richard Biener from comment #6) > Try -fno-tree-vectorize? I tried that, and it made no difference at all. I also tried dropping the -march= setting back to znver1 and that also made no

[Bug c/109093] New: csmith: a February runtime bug ?

2023-03-10 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109093 Bug ID: 109093 Summary: csmith: a February runtime bug ? Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c

[Bug middle-end/109192] timeout with -O3 -fno-var-tracking ?

2023-03-19 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109192 David Binderman changed: What|Removed |Added CC||amacleod at redhat dot com ---

[Bug middle-end/109192] timeout with -O3 -fno-var-tracking ?

2023-03-19 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109192 --- Comment #1 from David Binderman --- Current git range seems to be g:af22b54af53c0f2a .. g:f3b1af49702a3d19, which is 75 commits.

[Bug middle-end/109192] timeout with -O3 -fno-var-tracking ?

2023-03-19 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109192 --- Comment #2 from David Binderman --- Range now downto g:a0c2ea3ee6e47f40 .. g:2db1fd76ebaa6da8, which is 19 commits.

[Bug c/109192] New: timeout with -g -O3 -fno-var-tracking ?

2023-03-19 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109192 Bug ID: 109192 Summary: timeout with -g -O3 -fno-var-tracking ? Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c

[Bug c/109208] New: gcc doesn't detect when sizes are booleans

2023-03-20 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109208 Bug ID: 109208 Summary: gcc doesn't detect when sizes are booleans Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c

[Bug c/109219] New: csmith: ice in vect_slp_analyze_node_operations_1, at tree-vect-slp.cc:5954

2023-03-20 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109219 Bug ID: 109219 Summary: csmith: ice in vect_slp_analyze_node_operations_1, at tree-vect-slp.cc:5954 Product: gcc Version: 13.0 Status: UNCONFIRMED Severity:

[Bug c++/109274] New: ice in in_chain_p, at gimple-range-gori.cc:119

2023-03-24 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109274 Bug ID: 109274 Summary: ice in in_chain_p, at gimple-range-gori.cc:119 Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug target/109093] csmith: a February runtime bug ?

2023-03-10 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109093 --- Comment #1 from David Binderman --- Current git range is g:7478278f88ba1753 .. g:fea34ee491104f32 This is 7 commits. 6 of them seem to be libstdc++ and then there is this one: commit 866555b170016c49beb869a78cbecdeb07c63135 Author: Jakub

[Bug target/109093] csmith: a February runtime bug ?

2023-03-10 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109093 David Binderman changed: What|Removed |Added CC||jakub at redhat dot com --- Comment

[Bug target/109093] csmith: a February runtime bug ?

2023-03-10 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109093 --- Comment #3 from David Binderman --- Created attachment 54638 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54638=edit C source code This C code seems to fail in the same way. Possible duplicate.

[Bug target/109093] [13 regression] csmith: a February runtime bug ?

2023-03-10 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109093 --- Comment #4 from David Binderman --- Created attachment 54639 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54639=edit C source code A third example that fails at the same git hash.

[Bug middle-end/109031] csmith: possible bad code with -O2 -fno-strict-aliasing

2023-03-09 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109031 David Binderman changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED

[Bug middle-end/109031] csmith: possible bad code with -O2 -fno-strict-aliasing since r13-254-gdd3c7873a61019e9

2023-03-09 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109031 --- Comment #24 from David Binderman --- I tried experimenting with the flags that change -O1 into -O2 and got this: $ for i in ~/gcc/results.202205*/bin/gcc; do echo $i; $i -w -ftrivial-auto-var-init=zero -O1 -fno-strict-aliasing bug892.c &&

[Bug c/109056] cppcheck: no warning for suspicious return type

2023-03-07 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109056 --- Comment #3 from David Binderman --- (In reply to Andrew Pinski from comment #2) > Which turns on -Wsign-conversion . -Wsign-conversion seems close, but not quite right. The problem is in potential overflow, not sign conversion. -Woverflow

[Bug c/109056] New: cppcheck: no warning for suspicious return type

2023-03-07 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109056 Bug ID: 109056 Summary: cppcheck: no warning for suspicious return type Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug c/109237] New: csmith: another timeout with -g -O3 this time

2023-03-21 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109237 Bug ID: 109237 Summary: csmith: another timeout with -g -O3 this time Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c

[Bug middle-end/109237] csmith: another timeout with -g -O3 this time

2023-03-21 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109237 David Binderman changed: What|Removed |Added Keywords||needs-bisection, |

[Bug c/109184] New: csmith: really old bug with -O3

2023-03-18 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109184 Bug ID: 109184 Summary: csmith: really old bug with -O3 Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c

[Bug c/109184] csmith: really old bug with -O3

2023-03-18 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109184 David Binderman changed: What|Removed |Added Keywords||needs-bisection --- Comment #1 from

[Bug c/109184] csmith: really old bug with -O3

2023-03-18 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109184 --- Comment #2 from David Binderman --- Created attachment 54702 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54702=edit partially reduced C source code

[Bug c/109184] csmith: really old bug with -O3

2023-03-18 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109184 --- Comment #3 from David Binderman --- After checking the flags that move -O2 to -O3, flag -floop-interchange seems to be at fault. $ ~/gcc/results/bin/gcc -w -O2 -fno-strict-aliasing bug897.c $ ./a.out 1 > 1 $ ~/gcc/results/bin/gcc -w -O2

[Bug middle-end/109031] csmith: possible bad code with -O2 -fno-strict-aliasing

2023-03-06 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109031 --- Comment #2 from David Binderman --- (In reply to David Binderman from comment #1) > I will try to bisect this one with snapshots. Trying 20220515 first. This one bad. Trying 20220508.

[Bug middle-end/109031] csmith: possible bad code with -O2 -fno-strict-aliasing

2023-03-06 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109031 --- Comment #1 from David Binderman --- I will try to bisect this one with snapshots. Trying 20220515 first.

[Bug c/109139] New: ice in make_decl_rtl, at varasm.cc:1442

2023-03-15 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109139 Bug ID: 109139 Summary: ice in make_decl_rtl, at varasm.cc:1442 Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c

[Bug c++/108888] New: error: definition in block 26 follows the use

2023-02-22 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=10 Bug ID: 10 Summary: error: definition in block 26 follows the use Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug modula2/108944] New: libgm2/libm2pim/sckt.cc:254:3: warning: memset() called to fill 0 bytes. [memsetZeroBytes]

2023-02-27 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108944 Bug ID: 108944 Summary: libgm2/libm2pim/sckt.cc:254:3: warning: memset() called to fill 0 bytes. [memsetZeroBytes] Product: gcc Version: 13.0 Status: UNCONFIRMED

[Bug c/108959] New: ice in modify_assignment, at ipa-param-manipulation.cc:1905

2023-02-27 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108959 Bug ID: 108959 Summary: ice in modify_assignment, at ipa-param-manipulation.cc:1905 Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal

[Bug c/108959] ice in modify_assignment, at ipa-param-manipulation.cc:1905

2023-02-27 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108959 --- Comment #1 from David Binderman --- The bug first seems to occur sometime between git hash g:5c43f06c228d169c, dated 20230202 and g:f0065f207cf19cd9, dated 20230203.

[Bug c/108959] ice in modify_assignment, at ipa-param-manipulation.cc:1905

2023-02-27 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108959 --- Comment #2 from David Binderman --- Reduced code seems to be: union U2 { long f0; int f1 }; g_16; g_70[]; static func_61(int) { for (;;) g_70[g_16] = 4; } static func_43(int *p_44) { func_61(*p_44); } main() { union U2 l_38 =

[Bug ipa/108959] [13 Regression] ice in modify_assignment, at ipa-param-manipulation.cc:1905

2023-02-27 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108959 --- Comment #3 from David Binderman --- I will have a go at a git bisection.

[Bug ipa/108959] [13 Regression] ice in modify_assignment, at ipa-param-manipulation.cc:1905

2023-02-28 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108959 --- Comment #4 from David Binderman --- Only one pass at reduction, leaving 14 revisions, but this commit looks to be a hot candidate: commit e8109bd87766be88e83fe88a44433dae16358a02 Author: Martin Jambor Date: Fri Feb 3 13:28:24 2023

[Bug ipa/108959] [13 Regression] ice in modify_assignment, at ipa-param-manipulation.cc:1905

2023-02-28 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108959 David Binderman changed: What|Removed |Added CC||jamborm at gcc dot gnu.org ---

[Bug ipa/108959] [13 Regression] ice in modify_assignment, at ipa-param-manipulation.cc:1905

2023-02-28 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108959 --- Comment #6 from David Binderman --- As expected: $ git bisect bad e8109bd87766be88 e8109bd87766be88e83fe88a44433dae16358a02 is the first bad commit commit e8109bd87766be88e83fe88a44433dae16358a02 Author: Martin Jambor Date: Fri Feb 3

[Bug c/109025] ice in nested_in_vect_loop_p

2023-03-04 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109025 --- Comment #1 from David Binderman --- Reduced C code seems to be: g_86, g_472, g_1844, func_4_p_8; func_4() { int *l_3175 = _86; for (; g_1844; g_1844 -= 1) { g_472 = 1; for (; g_472; g_472 += 1) if (func_4_p_8)

[Bug c/109025] New: ice in nested_in_vect_loop_p

2023-03-04 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109025 Bug ID: 109025 Summary: ice in nested_in_vect_loop_p Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c

[Bug tree-optimization/109025] [13 Regression] ice in nested_in_vect_loop_p

2023-03-05 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109025 --- Comment #6 from David Binderman --- (In reply to David Binderman from comment #5) > (In reply to David Binderman from comment #4) > > I will have a go at a bisection. 825 git commits in the range. > > Current range seems to be

[Bug tree-optimization/109025] [13 Regression] ice in nested_in_vect_loop_p

2023-03-05 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109025 David Binderman changed: What|Removed |Added CC||rguenther at suse dot de --- Comment

[Bug tree-optimization/109025] [13 Regression] ice in nested_in_vect_loop_p

2023-03-05 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109025 --- Comment #4 from David Binderman --- (In reply to Andrew Pinski from comment #3) > Note using &, | or ^ causes the ICE. Using + or - or * does not. Interesting. > Here is more simplified testcase: Thanks for that. I will have a go at a

[Bug tree-optimization/109025] [13 Regression] ice in nested_in_vect_loop_p

2023-03-05 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109025 --- Comment #7 from David Binderman --- (In reply to David Binderman from comment #6) > Range now seems to be g:d699d32f47833cfa .. g:3b54cc9d04c2efb2, > with 52 commits in the range. Now downto g:0cbb756fe9c8e13a .. g:7e3ce73849fef8b5, with

[Bug tree-optimization/109025] [13 Regression] ice in nested_in_vect_loop_p

2023-03-05 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109025 --- Comment #5 from David Binderman --- (In reply to David Binderman from comment #4) > I will have a go at a bisection. 825 git commits in the range. Current range seems to be g:59ad8b684dd67e17 .. g:1191a412bb17a734, with 206 commits in the

[Bug c/109031] New: csmith: possible bad code with -O2 -fno-strict-aliasing

2023-03-05 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109031 Bug ID: 109031 Summary: csmith: possible bad code with -O2 -fno-strict-aliasing Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal

[Bug c/108825] New: error during GIMPLE pass: unrolljam

2023-02-16 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108825 Bug ID: 108825 Summary: error during GIMPLE pass: unrolljam Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c

[Bug tree-optimization/108825] [13 Regression] error during GIMPLE pass: unrolljam

2023-02-16 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108825 --- Comment #3 from David Binderman --- (In reply to David Binderman from comment #2) > Trying revision 1191a412bb17a734. Seems bad. Trying 59ad8b684dd67e17.

[Bug tree-optimization/108825] [13 Regression] error during GIMPLE pass: unrolljam

2023-02-16 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108825 David Binderman changed: What|Removed |Added CC||rguenther at suse dot de --- Comment

[Bug tree-optimization/108825] [13 Regression] error during GIMPLE pass: unrolljam

2023-02-16 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108825 --- Comment #4 from David Binderman --- git range now seems to be g:59ad8b684dd67e17 .. g:3b54cc9d04c2efb2, which is 103 commits.

<    3   4   5   6   7   8   9   10   11   >