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
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107090
--- Comment #9 from Andrew Pinski ---
Look at how ctz_table_index is done and used.
The matching is done in match.pd language and then inside
simplify_count_trailing_zeroes (tree-ssa-forwprop.cc) it is used
nop_atomic_bit_test_and_p is
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107090
vfdff changed:
What|Removed |Added
Attachment #53684|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107090
Andrew Pinski changed:
What|Removed |Added
Depends on||103216
--- Comment #6 from Andrew
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107090
vfdff changed:
What|Removed |Added
CC||zhongyunde at huawei dot com
--- Comment #5
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;
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107090
--- Comment #3 from Andrew Pinski ---
(In reply to vfdff from comment #2)
> 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
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.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107090
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2022-09-29
11 matches
Mail list logo