[Bug tree-optimization/95396] [8/9/10/11 Regression] GCC produces incorrect code with -O3 for loops since r8-6511-g3ae129323d150621

2020-07-06 Thread babokin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95396 --- Comment #4 from Dmitry Babokin --- Richard Sandiford, could you please have a look as author of the commit, which brought the regression? We have a bunch of other fails, which might be or might be not the same as this one. We'd like to

[Bug tree-optimization/95396] [8/9/10/11 Regression] GCC produces incorrect code with -O3 for loops since r8-6511-g3ae129323d150621

2020-06-14 Thread babokin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95396 --- Comment #3 from Dmitry Babokin --- Could anyone please have a look at this bug? Fixing it would help us not to file duplicate bugs discovered in random testing.

[Bug sanitizer/83382] UBSAN tiggers false-positive warning [-Werror=uninitialized]

2017-12-12 Thread babokin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83382 --- Comment #2 from Dmitry Babokin --- (In reply to Richard Biener from comment #1) > The interaction between sanitizers and middle-end emitted warnings is > difficult at best. Can you avoid -Werror when sanitizing? I can, if it's absolutely

[Bug tree-optimization/83383] New: Wrong code with a bunch of type conversion and ternary operators

2017-12-11 Thread babokin at gmail dot com
Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com Target Milestone: --- gcc trunk, rev 255537, x86_64. > cat f.cpp unsigned long long int tf_3_var_118 = 12702665990007799801ULL; unsigned c

[Bug sanitizer/83382] New: UBSAN tiggers false-positive warning [-Werror=uninitialized]

2017-12-11 Thread babokin at gmail dot com
Priority: P3 Component: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org, kcc at gcc dot gnu.org, marxin at gcc dot

[Bug target/83252] Wrong code with "-march=skylake-avx512 -O3"

2017-12-04 Thread babokin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83252 --- Comment #11 from Dmitry Babokin --- (In reply to Andrew Pinski from comment #10) > We can add this if needed. I think regression could be made make generic > and add a generic new bug component. We do have some very active people >

[Bug target/83252] Wrong code with "-march=skylake-avx512 -O3"

2017-12-04 Thread babokin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83252 --- Comment #9 from Dmitry Babokin --- (In reply to Richard Biener from comment #8) > I suppose one could try scripting something with -fdisable-{tree,rtl}-$dump > and seeding the list of passes to enable/disable with -fdump-{tree,rtl}-all. > >

[Bug target/83252] Wrong code with "-march=skylake-avx512 -O3"

2017-12-03 Thread babokin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83252 --- Comment #6 from Dmitry Babokin --- (In reply to Jakub Jelinek from comment #1) > Option bisection is rarely useful for GCC, debugging issues with -Ox -fthat > -fno-this -fwhatever is usually not beneficial over just -Ox or whatever > minimal

[Bug target/83252] Wrong code with "-march=skylake-avx512 -O3"

2017-12-03 Thread babokin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83252 --- Comment #5 from Dmitry Babokin --- The original test case is also fixed. Thanks for investigation.

[Bug target/83252] New: Wrong code with "-march=skylake-avx512 -O3"

2017-12-01 Thread babokin at gmail dot com
nt: target Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com Target Milestone: --- Created attachment 42775 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=42775=edit reproducer gcc trunk rev255248, x86_64. Attached test case produces wr

[Bug tree-optimization/83221] New: qsort comparator not anti-commutative: -2147483648, -2147483648

2017-11-29 Thread babokin at gmail dot com
Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com Target Milestone: --- Created attachment 42748 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=42748=edit reproducer gcc trunk rev255248, x86

[Bug ipa/82957] New: internal compiler error: in to_cgraph_frequency, at profile-count.c:251

2017-11-12 Thread babokin at gmail dot com
Priority: P3 Component: ipa Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com CC: marxin at gcc dot gnu.org Target Milestone: --- Building compiler-rt (LLVM libs) with GCC trunk (rev 254666, x86_64) I get this error

[Bug rtl-optimization/82778] New: crash: insn does not satisfy its constraints

2017-10-30 Thread babokin at gmail dot com
-optimization Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com Target Milestone: --- gcc trunk rev254211, x86_64. > cat f.cpp template struct c { typedef a d[b]; static a e(d f, int g) { return f[g]; } }; template struct B { typedef c<a

[Bug rtl-optimization/82576] New: sbitmap_vector_alloc() not ready for 64 bits

2017-10-16 Thread babokin at gmail dot com
-optimization Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com Target Milestone: --- Created attachment 42382 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=42382=edit Reproducer gcc trunk, rev253744, x86_64. Trying compile attached test c

[Bug rtl-optimization/81423] [6/7 Regression] Wrong code at -O2

2017-10-14 Thread babokin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81423 --- Comment #16 from Dmitry Babokin --- ll = -5597998501375493990LL; // result is 2595916314 here. ll = unsigned(5677365550390624949L - ll) - (ull1 > 0); So: // t1 is 466811183 unsigned long long int t1 = ll + -2129105131L; // t2 is

[Bug c/82413] New: -O0 crash (ICE in decompose, at tree.h:5179)

2017-10-02 Thread babokin at gmail dot com
Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com Target Milestone: --- GCC trunk, rev 253367, x86_64. Rev 253307 works fine, so it's a fresh regression. > cat f.cpp bool a; int b; void c() { b & <= 0; } > g++ -c f.cpp f.cpp: In fun

[Bug tree-optimization/82381] New: internal compiler error: qsort checking failed

2017-10-01 Thread babokin at gmail dot com
: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com Target Milestone: --- GCC trunk rev 253307, x86_64. This looks like a fresh regression. I see quite many fails like this one. > cat f.cpp char b, h; unsigned short c, e; short d, f

[Bug sanitizer/82353] runtime ubsan crash

2017-09-28 Thread babokin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82353 --- Comment #1 from Dmitry Babokin --- Created attachment 42256 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=42256=edit original test case I'm also attaching original test case, just in case. For the bug to reproduce it's important to

[Bug sanitizer/82353] New: runtime ubsan crash

2017-09-28 Thread babokin at gmail dot com
: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org, kcc at gcc dot gnu.org, marxin at gcc dot gnu.org Target Milestone: --- Created attachment 42255

[Bug tree-optimization/81814] New: Incorrect behaviour at -O0 (conditional operator)

2017-08-11 Thread babokin at gmail dot com
: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com Target Milestone: --- gcc trunk, x86_64. The test case is simple and my understanding that the correct result is 0x0100, while gcc produces 0. Slight massaging of the code (like

[Bug c++/81607] [6/7 Regression] Conditional operator: "type mismatch in shift expression" error

2017-08-08 Thread babokin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81607 --- Comment #12 from Dmitry Babokin --- The fix helped all fails that I see (with all 7 different symptoms). Thanks!

[Bug middle-end/81705] [8 Regression] UBSAN: yet another false positive

2017-08-04 Thread babokin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81705 --- Comment #7 from Dmitry Babokin --- That's an excellent new! This means UBSAN becomes finally fully functional in GCC. No known false positives anymore (on quite large test base). Great job and thank you!

[Bug tree-optimization/81705] New: UBSAN: yet another false positive

2017-08-03 Thread babokin at gmail dot com
-optimization Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com Target Milestone: --- gcc trunk, rev250857, x86_64. After recent fix for #81148, this case is the last one failing UBSAN false positive that I see on my radars. > cat f.cpp int var_4 = -1716607

[Bug tree-optimization/81607] New: Conditional operator: "type mismatch in shift expression" error

2017-07-28 Thread babokin at gmail dot com
ty: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com Target Milestone: --- gcc trunk, rev250630, x86_64. I see a lot of crashes involving conditional operator and struct field access. I see

[Bug tree-optimization/81588] New: Wrong code at -O2

2017-07-27 Thread babokin at gmail dot com
Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com Target Milestone: --- gcc trunk, rev250630, x86_64. > cat f.cpp #include long int var_34 = 5011877430933453486L; unsigned short var_82 = 24847; long int var_58 = 1; void foo() { if (var_82 > var_34

[Bug tree-optimization/81555] Wrong code at -O1

2017-07-26 Thread babokin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81555 --- Comment #4 from Dmitry Babokin --- (In reply to Marc Glisse from comment #3) > -fno-tree-reassoc should help both. It helps. > It is often a combination of optimizations that causes the bug. Reassoc is > doing a good transformation, but it

[Bug tree-optimization/81555] Wrong code at -O1

2017-07-26 Thread babokin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81555 --- Comment #2 from Dmitry Babokin --- Hmmm, but this one is triggered at -O1, another only at -O2.

[Bug tree-optimization/81556] New: Wrong code at -O2

2017-07-25 Thread babokin at gmail dot com
Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com Target Milestone: --- gcc trunk, rev250545, x86_64. This one seems to be different from previously reported bugs. Minimum opt level to trigger bug is -O2, switching slsr doesn't help (-fno-tree-slsr). > cat f.

[Bug tree-optimization/81555] New: Wrong code at -O1

2017-07-25 Thread babokin at gmail dot com
Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com Target Milestone: --- gcc trunk, rev250545, x86_64. > cat f.cpp #include unsigned int var_1 = 1; bool var_2 = false; unsigned int var_3 = 679743406U; unsigned int var_4 = 3054363510U; bool var_5 = true; unsig

[Bug rtl-optimization/81553] New: ICE in immed_wide_int_const, at emit-rtl.c:607

2017-07-25 Thread babokin at gmail dot com
-optimization Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com Target Milestone: --- gcc trunk, rev250527, x86_64 > cat f.cpp int a, b, c; struct d { static int e; } f; d g, h; void i() { f.e = (10834211066969351267ULL || 0) >> c

[Bug tree-optimization/81546] ICE at -O3 during GIMPLE pass dom

2017-07-25 Thread babokin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81546 --- Comment #2 from Dmitry Babokin --- Reduced test case consumes about 11Gb. That's a lot and looks like it's just the consequence of the real problem. But the test case in #81488 consumes 128Gb and dies on my machine because of lack of

[Bug tree-optimization/81503] [8 Regression] Wrong code at -O2

2017-07-24 Thread babokin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81503 --- Comment #6 from Dmitry Babokin --- How can I switch off optimization phases to workaround the bug? I have another instances of wrong code bugs, so I'd like to make sure that I don't create duplicate reports for the same problem.

[Bug tree-optimization/81546] New: ICE at -O3 during GIMPLE pass dom

2017-07-24 Thread babokin at gmail dot com
-optimization Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com Target Milestone: --- Created attachment 41823 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=41823=edit reduced and original test cases gcc trunk rev250367, x86_64 Test case is reduced f

[Bug tree-optimization/81503] New: Wrong code at -O2

2017-07-20 Thread babokin at gmail dot com
Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com Target Milestone: --- gcc trunk, rev250367, x86_64. > cat f.cpp #include unsigned short a = 41461; unsigned short b = 3419; int c = 0; void foo() { if (a + b * ~(0 != 5)) c = -~(b * ~(0 != 5)) + 2147483

[Bug tree-optimization/81488] New: gcc goes off the limits allocating memory in gimple-ssa-strength-reduction.c

2017-07-19 Thread babokin at gmail dot com
: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com Target Milestone: --- Created attachment 41792 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=41792=edit reproducer gcc tr

[Bug tree-optimization/81423] New: Wrong code at -O2

2017-07-12 Thread babokin at gmail dot com
Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com Target Milestone: --- gcc trunk, rev250140, x86_64. Test case has no undefined behavior, but -O2 produces incorrect result. > cat f.cpp #include unsigned long long int ll = 0; unsigned long long int ull1 = 1

[Bug tree-optimization/81403] New: wrong code at -O3

2017-07-11 Thread babokin at gmail dot com
Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com Target Milestone: --- gcc rev250140, x86_64. > cat f.cpp #include short var_9 = 19581; unsigned char var_33 = 21; long int var_55 = 286697804684061197L; long int var_59 = -1962393262513510540L; long int var

[Bug sanitizer/81387] UBSAN consumes too much memory at -O2

2017-07-11 Thread babokin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81387 --- Comment #3 from Dmitry Babokin --- Interesting that you've mentioned -fno-sanitize-recover, I haven't realized that it has effect on the number of basic blocks. But by default I run "-fsanitize=undefined -fno-sanitize-recover=undefined", so

[Bug sanitizer/81387] New: UBSAN consumes too much memory at -O2

2017-07-10 Thread babokin at gmail dot com
Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org, kcc at gcc dot gnu.org, marxin at gcc dot gnu.org Target Milestone: --- Created

[Bug rtl-optimization/81332] GCC crash during "RTL pass: expand" - verify_flow_info: REG_BR_PROB does not match cfg

2017-07-10 Thread babokin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81332 --- Comment #1 from Dmitry Babokin --- I've jut hit another instance on this bug, which mean that it's probably not too rare and quite possible to hit in the wild.

[Bug rtl-optimization/81332] New: GCC crash during "RTL pass: expand" - verify_flow_info: REG_BR_PROB does not match cfg

2017-07-05 Thread babokin at gmail dot com
NCONFIRMED Severity: normal Priority: P3 Component: rtl-optimization Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com Target Milestone: --- gcc rev250008, x86_64. > cat f.cpp extern int var_8, var_18, var_29, var_1365; long a;

[Bug sanitizer/81281] New: UBSAN: false positive, dropped promotion to long type.

2017-07-02 Thread babokin at gmail dot com
Component: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org, kcc at gcc dot gnu.org, marxin at gcc dot gnu.org Target Milestone

[Bug tree-optimization/81162] New: UBSAN switch triggers incorrect optimization

2017-06-21 Thread babokin at gmail dot com
-optimization Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com Target Milestone: --- gcc trunk rev249427, x86_64 In presence of -fsanitize=undefined optimisations (-O2) produce wrong code. > cat f.cpp #include short s; int i1 = 1; int i2

[Bug sanitizer/81148] New: UBSAN: two more false positives

2017-06-20 Thread babokin at gmail dot com
Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org, kcc at gcc dot gnu.org, marxin at gcc dot gnu.org Target Milestone: --- gcc rev249427

[Bug sanitizer/81097] New: UBSAN: false positive for not existing negation operator and a bogus message

2017-06-14 Thread babokin at gmail dot com
: normal Priority: P3 Component: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org, kcc at gcc dot gnu.org

[Bug sanitizer/81065] UBSAN: false positive as a result of distribution involving different types

2017-06-13 Thread babokin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81065 --- Comment #5 from Dmitry Babokin --- Thanks for blazingly fast fixes. This enables filing more bugs, as it's difficult to distinguish between unrelated fails before one of them is actually fixed.

[Bug sanitizer/81088] New: UBSAN: false positive as a result of reassosiation

2017-06-13 Thread babokin at gmail dot com
: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org, kcc at gcc dot gnu.org, marxin at gcc dot gnu.org Target Milestone

[Bug sanitizer/81065] New: UBSAN: false positive as a result of distribution involving different types

2017-06-11 Thread babokin at gmail dot com
: normal Priority: P3 Component: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org, kcc at gcc dot gnu.org

[Bug middle-end/66313] Unsafe factorization of a*b+a*c

2017-05-31 Thread babokin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66313 --- Comment #20 from Dmitry Babokin --- I've created #80932 for c1*(c2*v1-c3*v2)=>c1*c2*v1-c1*c3*v2 issue. --- Comment #21 from Dmitry Babokin --- I've created #80932 for c1*(c2*v1-c3*v2)=>c1*c2*v1-c1*c3*v2 issue.

[Bug middle-end/66313] Unsafe factorization of a*b+a*c

2017-05-31 Thread babokin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66313 --- Comment #20 from Dmitry Babokin --- I've created #80932 for c1*(c2*v1-c3*v2)=>c1*c2*v1-c1*c3*v2 issue. --- Comment #21 from Dmitry Babokin --- I've created #80932 for c1*(c2*v1-c3*v2)=>c1*c2*v1-c1*c3*v2 issue.

[Bug sanitizer/80932] New: UBSAN: false positive as a result of distribution: c1*(c2*v1-c3*v2)=>c1*c2*v1-c1*c3*v2

2017-05-31 Thread babokin at gmail dot com
MED Severity: normal Priority: P3 Component: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org, kcc at gcc

[Bug middle-end/66313] Unsafe factorization of a*b+a*c

2017-05-30 Thread babokin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66313 --- Comment #17 from Dmitry Babokin --- Any chances for the fix for this bug? Looks like this one stands as a last obstacle to claim UBSAN in GCC fully functional. I still see quite a few errors, but looks like all of them are attributed to

[Bug sanitizer/80875] New: UBSAN: compile time crash in fold_binary_loc at fold-const.c:9817

2017-05-24 Thread babokin at gmail dot com
Priority: P3 Component: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org, kcc at gcc dot gnu.org, marxin at gcc

[Bug middle-end/66313] Unsafe factorization of a*b+a*c

2017-05-23 Thread babokin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66313 --- Comment #16 from Dmitry Babokin --- Here's another test case with a contrary example, where a variable gets pulled into the braces and it also causes false positive. Transformation is: const1 * (const2 * var1 - const3 * var2) =>

[Bug ipa/80597] [8 Regression] internal compiler error: in compute_inline_parameters, at ipa-inline-analysis.c:3126

2017-05-23 Thread babokin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80597 --- Comment #17 from Dmitry Babokin --- Yes, it's fix with current trunk.

[Bug middle-end/66313] Unsafe factorization of a*b+a*c

2017-05-22 Thread babokin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66313 --- Comment #15 from Dmitry Babokin --- The bug is almost 2 years old. I consider it's quite important, as false positives make UBSAN not usable on any large codebases.

[Bug sanitizer/80847] UBSAN: yet another false positive (part2)

2017-05-21 Thread babokin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80847 Dmitry Babokin changed: What|Removed |Added CC||babokin at gmail dot com

[Bug sanitizer/80847] New: UBSAN: yet another false positive (part2)

2017-05-21 Thread babokin at gmail dot com
: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org, kcc at gcc dot gnu.org, marxin at gcc dot gnu.org Target Milestone: --- gcc

[Bug ipa/80597] [8 Regression] internal compiler error: in compute_inline_parameters, at ipa-inline-analysis.c:3126

2017-05-17 Thread babokin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80597 --- Comment #14 from Dmitry Babokin --- Disregard my previous comment. Original test case still fails with compiler switches that I've originally reported (-fsanitize=undefined).

[Bug ipa/80597] [8 Regression] internal compiler error: in compute_inline_parameters, at ipa-inline-analysis.c:3126

2017-05-17 Thread babokin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80597 --- Comment #13 from Dmitry Babokin --- The attached patch fixes my original test case.

[Bug sanitizer/80800] New: UBSAN: yet another false positive

2017-05-17 Thread babokin at gmail dot com
Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org, kcc at gcc dot gnu.org, marxin at gcc dot gnu.org Target Milestone: --- gcc rev248130

[Bug sanitizer/80386] UBSAN: false positive - constant folding and reassosiation before instrumentation

2017-05-16 Thread babokin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80386 --- Comment #8 from Dmitry Babokin --- Many failing tests are fixed, but quite few still failing. Should I add failing test cases here or create a separate bug?

[Bug ipa/80597] New: internal compiler error: in compute_inline_parameters, at ipa-inline-analysis.c:3126

2017-05-02 Thread babokin at gmail dot com
Severity: normal Priority: P3 Component: ipa Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com Target Milestone: --- Created attachment 41299 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=41299=edit reproducer gcc top of the tr

[Bug sanitizer/80536] New: UBSAN: compile time segfault

2017-04-26 Thread babokin at gmail dot com
Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org, kcc at gcc dot gnu.org Target Milestone: --- > cat f.cpp extern unsigned char var_67; v

[Bug sanitizer/80349] [6 Regression] UBSAN: compile time crash with "type mismatch in binary expression" message

2017-04-25 Thread babokin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80349 --- Comment #12 from Dmitry Babokin --- int var; long a; long foo() { int i = !(1 & 808U ^ 1 & var) >> 0; long l = 0 % ((a & 1) != (3053241240409UL & 1)); return i+l; }

[Bug sanitizer/80349] [6 Regression] UBSAN: compile time crash with "type mismatch in binary expression" message

2017-04-24 Thread babokin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80349 --- Comment #8 from Dmitry Babokin --- I also see crashes reporting problems with ^ operator.

[Bug sanitizer/80349] [6 Regression] UBSAN: compile time crash with "type mismatch in binary expression" message

2017-04-21 Thread babokin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80349 --- Comment #7 from Dmitry Babokin --- One more. GCC r247062. > cat f.cpp unsigned long int ll; int foo() { return (2036854775807 >> ll & char(207648476159223) | 502810590243120797UL) << 0; } > g++ -fsanitize=undefined -O0 -c f.cpp f.cpp: In

[Bug sanitizer/80386] UBSAN: false positive - constant folding and reassosiation before instrumentation

2017-04-17 Thread babokin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80386 --- Comment #4 from Dmitry Babokin --- Any update? This bug makes gcc ubsan implementation almost unusable on any real application.

[Bug sanitizer/80403] UBSAN: compile time crash with "type mismatch in binary expression" message in / and % expr

2017-04-13 Thread babokin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80403 --- Comment #11 from Dmitry Babokin --- I confirm that the latest patch fixes all UBSAN compile time problems that I have. Thanks! Though correctness issues remain - PR80386.

[Bug sanitizer/80403] UBSAN: compile time crash with "type mismatch in binary expression" message in / and % expr

2017-04-12 Thread babokin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80403 --- Comment #8 from Dmitry Babokin --- Three errors in one test case. GCC r246882. > cat f.cpp extern const long long int var_7; extern unsigned long int var_59; int foo() { int a = (0 - 40U <= (0 == 8)) << !var_59 << (0 < var_7) == 0; int

[Bug sanitizer/80403] UBSAN: compile time crash with "type mismatch in binary expression" message in / and % expr

2017-04-12 Thread babokin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80403 --- Comment #7 from Dmitry Babokin --- 80404 and 80405 seemed similar, but different to me, so I decided to report them separately. Anyway, after the latest fixes I still see 2 compile crashes. I'm reducing them and will report here.

[Bug sanitizer/80405] New: UBSAN: compile time crash with "type mismatch in shift expression" error

2017-04-11 Thread babokin at gmail dot com
ty: normal Priority: P3 Component: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org, kcc at gcc dot gnu.or

[Bug sanitizer/80404] New: UBSAN: compile time crash with "non-trivial conversion at assignment" error

2017-04-11 Thread babokin at gmail dot com
Severity: normal Priority: P3 Component: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org, kcc at gcc d

[Bug sanitizer/80403] New: UBSAN: compile time crash with "type mismatch in binary expression" message in / and % expr

2017-04-11 Thread babokin at gmail dot com
NCONFIRMED Severity: normal Priority: P3 Component: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org,

[Bug sanitizer/80386] New: UBSAN: false positive - constant folding and reassosiation before instrumentation

2017-04-10 Thread babokin at gmail dot com
: normal Priority: P3 Component: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org, kcc at gcc dot gnu.org

[Bug sanitizer/80349] [6/7 Regression] UBSAN: compile time crash with "type mismatch in binary expression" message

2017-04-10 Thread babokin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80349 --- Comment #3 from Dmitry Babokin --- PR80348 is fixed, but this still fails.

[Bug sanitizer/80348] [6 Regression] UBSAN: compile time crash in ubsan_instrument_division

2017-04-07 Thread babokin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80348 --- Comment #7 from Dmitry Babokin --- These tests are still failing: > cat f1.cpp void foo() { 0 / unsigned(!(0 - 3) >= (0 > 0)); } > cat f2.cpp extern long long int var_58; void foo() { (0 >= 10253361740180 >= long(0 >= 0)) % var_58; } > cat

[Bug sanitizer/80348] UBSAN: compile time crash in ubsan_instrument_division

2017-04-06 Thread babokin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80348 --- Comment #1 from Dmitry Babokin --- *** Bug 80347 has been marked as a duplicate of this bug. ***

[Bug sanitizer/80347] UBSAN: compile time crash in ubsan_instrument_division

2017-04-06 Thread babokin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80347 Dmitry Babokin changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug sanitizer/80350] New: UBSAN changes code semantics when -fno-sanitize-recover=undefined is used

2017-04-06 Thread babokin at gmail dot com
Priority: P3 Component: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org, kcc at gcc dot gnu.org Target

[Bug sanitizer/80349] New: UBSAN: compile time crash with "type mismatch in binary expression" message

2017-04-06 Thread babokin at gmail dot com
Severity: normal Priority: P3 Component: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org, kcc at gcc d

[Bug sanitizer/80348] New: UBSAN: compiler time crash in ubsan_instrument_division

2017-04-06 Thread babokin at gmail dot com
Priority: P3 Component: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org, kcc at gcc dot gnu.org Target Milestone

[Bug sanitizer/80347] New: UBSAN: compiler time crash in ubsan_instrument_division

2017-04-06 Thread babokin at gmail dot com
Priority: P3 Component: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org, kcc at gcc dot gnu.org Target Milestone

[Bug regression/80297] New: Compiler time crash: type mismatch in binary expression

2017-04-03 Thread babokin at gmail dot com
Priority: P3 Component: regression Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com Target Milestone: --- Top of the tree gcc crashes when compiler the following test case. Gcc 4.8 works well. > cat f.cpp extern const unsigned long int var

[Bug middle-end/79399] GCC fails to compile big source at -O0

2017-02-07 Thread babokin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79399 --- Comment #11 from Dmitry Babokin --- With new patch it compiled successfully. It took 41G of memory and 5:25 hours to complete.

[Bug middle-end/79399] GCC fails to compile big source at -O0

2017-02-07 Thread babokin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79399 --- Comment #7 from Dmitry Babokin --- It crashed. > /usr/bin/time --format="Max %M kb\nreal %E\nuser %U\nsys%S" g++ -std=c++11 -w > -O0 -march=nehalem -o gcc_no_opt_func.o -c func.cpp func.cpp: In function ‘void foo()’: func.cpp:26656:1:

[Bug middle-end/79399] GCC fails to compile big source at -O0

2017-02-07 Thread babokin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79399 --- Comment #6 from Dmitry Babokin --- I've started the compilation, it should take more than an hour to finish. Will report back when it's done.

[Bug middle-end/79399] GCC fails to compile big source at -O0

2017-02-07 Thread babokin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79399 --- Comment #4 from Dmitry Babokin --- The purpose of the generator is to break a compiler, that's why it's a single function in this case, but not many. Though with smaller functions we break compilers too. This is the generator:

[Bug middle-end/79399] New: GCC fails to compile big source at -O0

2017-02-06 Thread babokin at gmail dot com
-end Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com Target Milestone: --- The bug report is not very typical, but it may help fixing the real issue, which is hard to find and debug in other corricumstances. I don't mind if it's closed

[Bug middle-end/78769] [7 Regression] Incorrect arithmetic optimization for (a < 0) << 29 >> 1;

2016-12-10 Thread babokin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78769 --- Comment #2 from Dmitry Babokin --- I've used r243504, the latest available on git://gcc.gnu.org/git/gcc.git

[Bug middle-end/78769] New: [7 Regression] Incorrect arithmetic optimization for (a < 0) << 29 >> 1;

2016-12-10 Thread babokin at gmail dot com
everity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com Target Milestone: --- > cat bug.cpp #include char a = -110; unsigned long long int b; void foo(); int main() { foo(); pr

[Bug middle-end/78726] New: [5/6/7 Regression] Incorrect unsigned arithmetic optimization

2016-12-07 Thread babokin at gmail dot com
Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com Target Milestone: --- Created attachment 40279 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40279=edit reproducer -O2 produces different result t

[Bug target/78720] New: [7 Regression] Illegal instruction in generated code

2016-12-07 Thread babokin at gmail dot com
Component: target Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com Target Milestone: --- Created attachment 40278 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40278=edit reproducer > g++ -O2 -march=nehalem -o opt illegal_in

[Bug target/78438] New: incorrect comparison optimization

2016-11-20 Thread babokin at gmail dot com
Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com Target Milestone: --- Created attachment 40093 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40093=edit reproducer > g++ -O0 main.cpp func.cpp -o no_opt; ./no_opt 0 > g++ -O1 main.cpp func.c

[Bug target/78436] New: incorrect write to larger-than-type bitfield (signed char x:9)

2016-11-20 Thread babokin at gmail dot com
Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com Target Milestone: --- Created attachment 40091 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40091=edit reproducer The test is correct C++ prog

[Bug tree-optimization/77544] New: [Regression 6/7] segfault at -O0 - infinite loop in simplification

2016-09-09 Thread babokin at gmail dot com
Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com Target Milestone: --- Created attachment 39594 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=39594=edit reproducer > g++ -O0 -c func

[Bug target/77476] New: [Regression 7] [AVX-512] illegal kmovb instruction on KNL

2016-09-04 Thread babokin at gmail dot com
Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com Target Milestone: --- Created attachment 39554 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=39554=edit reproducer > g++ -std=c++11 -O3 -march=knl

[Bug tree-optimization/73714] New: [Regression 7] Incorrect unsigned long long arithmetic optimization

2016-08-11 Thread babokin at gmail dot com
Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com Target Milestone: --- Test case: #include int var_s2 = 0; int main () { unsigned long long a = 1ULL << (57 - var_s2); //

[Bug tree-optimization/72835] New: [Regression 7] Incorrect arithmetic optimization involving bitfield arguments

2016-08-08 Thread babokin at gmail dot com
: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: babokin at gmail dot com Target Milestone: --- Created attachment 39074 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=39074=edit reproducer -O0 and