[Bug c++/115240] New: [alias] Does we assume the math function have pure attribute ?

2024-05-27 Thread zhongyunde at huawei dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115240 Bug ID: 115240 Summary: [alias] Does we assume the math function have pure attribute ? Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: normal

[Bug c/112306] New: [AArch64][neon] incorrect combine the (a -1)* b into fnmsub for fixed vector type

2023-10-31 Thread zhongyunde at huawei dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112306 Bug ID: 112306 Summary: [AArch64][neon] incorrect combine the (a -1)* b into fnmsub for fixed vector type Product: gcc Version: 13.1.0 Status: UNCONFIRMED

[Bug c/111584] New: [aarch64] Redundant movprfx with ptrue

2023-09-25 Thread zhongyunde at huawei dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111584 Bug ID: 111584 Summary: [aarch64] Redundant movprfx with ptrue Product: gcc Version: 13.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c

[Bug c/110638] New: [13 regression] memcpy should be inlined with sve loop

2023-07-12 Thread zhongyunde at huawei dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110638 Bug ID: 110638 Summary: [13 regression] memcpy should be inlined with sve loop Product: gcc Version: 13.1.0 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug c/110103] New: the pointers return from two malloc is not equal

2023-06-03 Thread zhongyunde at huawei dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110103 Bug ID: 110103 Summary: the pointers return from two malloc is not equal Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3

[Bug c/109269] [sve] should check the upper bound for predicate sve

2023-03-23 Thread zhongyunde at huawei dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109269 --- Comment #3 from vfdff --- * test: https://gcc.godbolt.org/z/5s4Wbs466 ``` void mset (int *a, int num) { for (int i=0; i< num; i++) a[i] = 2; } ``` * the issue is still exist with int type as we use 32-bits register? . see detail on

[Bug c/109269] New: [sve] should check the upper bound for predicate sve

2023-03-23 Thread zhongyunde at huawei dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109269 Bug ID: 109269 Summary: [sve] should check the upper bound for predicate sve Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug c/108818] New: [aarch64] use a extra mov instruction compare to llvm

2023-02-16 Thread zhongyunde at huawei dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108818 Bug ID: 108818 Summary: [aarch64] use a extra mov instruction compare to llvm Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug middle-end/106323] [Suboptimal] memcmp(s1, s2, n) == 0 expansion on AArch64 compare to llvm

2022-12-06 Thread zhongyunde at huawei dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106323 --- Comment #4 from vfdff --- Now, llvm use 4 loads and CMP+CCMP, https://gcc.godbolt.org/z/PM3jxEM9M

[Bug target/104611] memcmp/strcmp/strncmp can be optimized when the result is tested for [in]equality with 0 on aarch64

2022-10-29 Thread zhongyunde at huawei dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104611 --- Comment #3 from vfdff --- As the load instructions usually have long latency, so do it need some extra restrict when we try this transformation?

[Bug tree-optimization/107090] [aarch64] sequence logic should be combined with mul and umulh

2022-10-28 Thread zhongyunde at huawei dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107090 --- Comment #11 from vfdff --- Created attachment 53787 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53787=edit has different operand order base on different commit node hi @Andrew Pinski * Showed as the figure swap_order.jpg

[Bug target/107316] [aarch64] Init big const value should be improved compare to llvm

2022-10-22 Thread zhongyunde at huawei dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107316 --- Comment #2 from vfdff --- (In reply to Andrew Pinski from comment #1) > I suspect this is just a dup of bug 106583 and will be fixed by the patch > which was submitted recently >

[Bug c/107359] New: [aarch64] should avoid the punpklo/punpkhi compare to llvm

2022-10-22 Thread zhongyunde at huawei dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107359 Bug ID: 107359 Summary: [aarch64] should avoid the punpklo/punpkhi compare to llvm Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal

[Bug c/107316] New: [aarch64] Init big const value should be improved compare to llvm

2022-10-19 Thread zhongyunde at huawei dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107316 Bug ID: 107316 Summary: [aarch64] Init big const value should be improved compare to llvm Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal

[Bug target/104611] memcmp/strcmp/strncmp can be optimized when the result is tested for [in]equality with 0 on aarch64

2022-10-18 Thread zhongyunde at huawei dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104611 vfdff changed: What|Removed |Added CC||zhongyunde at huawei dot com --- Comment #2

[Bug middle-end/107208] [aarch64] _complex integer return types could be improved

2022-10-13 Thread zhongyunde at huawei dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107208 --- Comment #3 from vfdff --- it seems releted to targetm.calls.function_value called by assign_parms, who return different behaviour for MODE_COMPLEX_FLOAT and MODE_COMPLEX_INT. With the following changes, then choose a pair of DI for the int

[Bug tree-optimization/107090] [aarch64] sequence logic should be combined with mul and umulh

2022-10-12 Thread zhongyunde at huawei dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107090 --- Comment #10 from vfdff --- Created attachment 53698 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53698=edit the huge bb sligtly change after match ResLo Thanks for your suggestion, and I think both ctz_table_index and

[Bug tree-optimization/107090] [aarch64] sequence logic should be combined with mul and umulh

2022-10-12 Thread zhongyunde at huawei dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107090 --- Comment #8 from vfdff --- hi @Andrew Pinski For the 2nd issue, I also matched the huge pattern, but it need return two value, it seems don't work with current framework? so should I have to split it into two simples to match the high and

[Bug c++/107208] New: [aarch64] llvm generate better code than gcc base on _Complex type mul

2022-10-10 Thread zhongyunde at huawei dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107208 Bug ID: 107208 Summary: [aarch64] llvm generate better code than gcc base on _Complex type mul Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal

[Bug tree-optimization/107090] [aarch64] sequence logic should be combined with mul and umulh

2022-10-10 Thread zhongyunde at huawei dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107090 vfdff changed: What|Removed |Added Attachment #53684|0 |1 is obsolete|

[Bug tree-optimization/107090] [aarch64] sequence logic should be combined with mul and umulh

2022-10-09 Thread zhongyunde at huawei dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107090 vfdff changed: What|Removed |Added CC||zhongyunde at huawei dot com --- Comment #5

[Bug c++/107190] New: [aarch64] regression with optimization -fexpensive-optimizations

2022-10-09 Thread zhongyunde at huawei dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107190 Bug ID: 107190 Summary: [aarch64] regression with optimization -fexpensive-optimizations Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal

[Bug tree-optimization/107090] [aarch64] sequence logic should be combined with mul and umulh

2022-10-07 Thread zhongyunde at huawei dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107090 --- Comment #4 from vfdff --- (In reply to Andrew Pinski from comment #1) > A few issues. > First is: > > if (_26 != 0) > goto ; [50.00%] > else > goto ; [50.00%] > >[local count: 536870913]: > ht_15 = ht_13 + 4294967296; >

[Bug tree-optimization/107090] [aarch64] sequence logic should be combined with mul and umulh

2022-10-01 Thread zhongyunde at huawei dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107090 --- Comment #2 from vfdff --- Thanks for your suggestion. As the combine pass can't address more than 4 sequence insns, which pass may be more suitable to match the huge pattern after fixing the 1st issue.

[Bug c/107090] New: [aarch64] sequence logic should be combined with mul and umulh

2022-09-29 Thread zhongyunde at huawei dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107090 Bug ID: 107090 Summary: [aarch64] sequence logic should be combined with mul and umulh Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal

[Bug fortran/106954] New: [12 Regression] compiler fail base on gfortran

2022-09-16 Thread zhongyunde at huawei dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106954 Bug ID: 106954 Summary: [12 Regression] compiler fail base on gfortran Product: gcc Version: 12.1.0 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug fortran/106353] New: [suboptimal] Why is a 3D array initialized, use case 2 two-layer loop?

2022-07-19 Thread zhongyunde at huawei dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106353 Bug ID: 106353 Summary: [suboptimal] Why is a 3D array initialized, use case 2 two-layer loop? Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal

[Bug c/106323] New: [Suboptimal] memcmp(s1, s2, n) == 0 expansion on AArch64 compare to llvm

2022-07-16 Thread zhongyunde at huawei dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106323 Bug ID: 106323 Summary: [Suboptimal] memcmp(s1, s2, n) == 0 expansion on AArch64 compare to llvm Product: gcc Version: 13.0 Status: UNCONFIRMED Severity:

[Bug tree-optimization/106268] [suboptimal] Remove unnecessary loops releated to fortran compare to ifort

2022-07-12 Thread zhongyunde at huawei dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106268 --- Comment #2 from vfdff --- it seems different for the C version, see detail https://godbolt.org/z/vc1edYKhf in your above case, the icc also doesn't elide the outer loop.

[Bug fortran/106268] New: [suboptimal] Remove unnecessary loops releated to fortran compare to ifort

2022-07-12 Thread zhongyunde at huawei dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106268 Bug ID: 106268 Summary: [suboptimal] Remove unnecessary loops releated to fortran compare to ifort Product: gcc Version: 13.0 Status: UNCONFIRMED Severity:

[Bug c/106255] New: [suboptinal] llvm uses instructions with larger access bit width

2022-07-11 Thread zhongyunde at huawei dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106255 Bug ID: 106255 Summary: [suboptinal] llvm uses instructions with larger access bit width Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal

[Bug c/106254] New: [suboptinal] llvm uses instructions with larger access bit width

2022-07-11 Thread zhongyunde at huawei dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106254 Bug ID: 106254 Summary: [suboptinal] llvm uses instructions with larger access bit width Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal

[Bug c/106200] New: Shrink-wrapping opportunity releated to function call

2022-07-05 Thread zhongyunde at huawei dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106200 Bug ID: 106200 Summary: Shrink-wrapping opportunity releated to function call Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug c/106146] New: [instcombine] a redundant movprfx insn compare to llvm

2022-06-30 Thread zhongyunde at huawei dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106146 Bug ID: 106146 Summary: [instcombine] a redundant movprfx insn compare to llvm Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug c/105181] New: [optimization] gcc generate worse code than clang base on neon

2022-04-06 Thread zhongyunde at huawei dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105181 Bug ID: 105181 Summary: [optimization] gcc generate worse code than clang base on neon Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal

[Bug c/104045] New: [AArch64] combine related to insn fmaxnm

2022-01-15 Thread zhongyunde at huawei dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104045 Bug ID: 104045 Summary: [AArch64] combine related to insn fmaxnm Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c

[Bug tree-optimization/94084] Optimizer produces suboptimal code related to loop-invariant

2021-06-23 Thread zhongyunde at huawei dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94084 vfdff changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug c++/101119] New: Missing the check about modify global variable for __attribute__((const)) function

2021-06-18 Thread zhongyunde at huawei dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101119 Bug ID: 101119 Summary: Missing the check about modify global variable for __attribute__((const)) function Product: gcc Version: 10.3.0 Status: UNCONFIRMED

[Bug c/100697] New: Missing fwprop for argument register

2021-05-20 Thread zhongyunde at huawei dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100697 Bug ID: 100697 Summary: Missing fwprop for argument register Product: gcc Version: 10.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c