https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90270
Jakub Jelinek changed:
What|Removed |Added
Target Milestone|8.4 |8.5
--- Comment #14 from Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90270
--- Comment #13 from jojo ---
Hi, guys,
Any solution for this issue ?
My be the following patch is choice :) ?
Are there issue with applied this patch ?
--- tree-ssa-loop-ivopts-orig.c 2019-05-17 09:32:58.05200 +0800
+++ tree-ssa-loop-iv
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90270
--- Comment #12 from rguenther at suse dot de ---
On Mon, 29 Apr 2019, amker at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90270
>
> --- Comment #10 from bin cheng ---
> (In reply to Richard Biener from comment #9)
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90270
--- Comment #11 from bin cheng ---
For the record, this test reveals another issue that original iv cand is not
considered:
Group 0:
Type: REFERENCE ADDRESS
Use 0.0:
At stmt:_1 = final_counts[i_21];
At pos: final_counts[i_21]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90270
--- Comment #10 from bin cheng ---
(In reply to Richard Biener from comment #9)
> (In reply to bin cheng from comment #7)
> > Also, when calling move_fixed_address_to_symbol, fixed_address_object_p
> > looks too restricted, it only considers link
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90270
--- Comment #8 from Richard Biener ---
(In reply to Andrew Pinski from comment #5)
> (In reply to bin cheng from comment #4)
> > On AArch64, iovpts generates following code:
> >[local count: 954449108]:
> > # crc_20 = PHI
> > # ivtmp.5_1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90270
--- Comment #9 from Richard Biener ---
(In reply to bin cheng from comment #7)
> Also, when calling move_fixed_address_to_symbol, fixed_address_object_p
> looks too restricted, it only considers link time constant address. In this
> case, it's a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90270
--- Comment #7 from bin cheng ---
Also, when calling move_fixed_address_to_symbol, fixed_address_object_p looks
too restricted, it only considers link time constant address. In this case,
it's an array object in stack.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90270
--- Comment #6 from bin cheng ---
(In reply to Andrew Pinski from comment #5)
> (In reply to bin cheng from comment #4)
> > On AArch64, iovpts generates following code:
> >[local count: 954449108]:
> > # crc_20 = PHI
> > # ivtmp.5_18 = P
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90270
--- Comment #5 from Andrew Pinski ---
(In reply to bin cheng from comment #4)
> On AArch64, iovpts generates following code:
>[local count: 954449108]:
> # crc_20 = PHI
> # ivtmp.5_18 = PHI <1(2), ivtmp.5_17(5)>
> _19 = &final_counts +
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90270
--- Comment #4 from bin cheng ---
On AArch64, iovpts generates following code:
[local count: 954449108]:
# crc_20 = PHI
# ivtmp.5_18 = PHI <1(2), ivtmp.5_17(5)>
_19 = &final_counts + 18446744073709551612;
_1 = MEM[base: _19, index: iv
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90270
Richard Biener changed:
What|Removed |Added
Priority|P3 |P2
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90270
--- Comment #3 from jojo ---
Haha..., get_address_cost() will cost down some address which is not my
expected, you
can get that code from my the 1st comment, i can not understand why adding that
code
in new version :(
(In reply to Andrew Pinski
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90270
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90270
Andrew Pinski changed:
What|Removed |Added
Known to work||7.3.0
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90270
Andrew Pinski changed:
What|Removed |Added
Keywords||missed-optimization
Target|
16 matches
Mail list logo