https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66768
amker at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|--
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66768
--- Comment #12 from amker at gcc dot gnu.org ---
Author: amker
Date: Thu Mar 2 11:25:11 2017
New Revision: 245837
URL: https://gcc.gnu.org/viewcvs?rev=245837&root=gcc&view=rev
Log:
PR tree-optimization/66768
* tree-ssa-loop-ivop
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66768
--- Comment #11 from Richard Henderson ---
Author: rth
Date: Mon Nov 9 09:18:16 2015
New Revision: 229997
URL: https://gcc.gnu.org/viewcvs?rev=229997&root=gcc&view=rev
Log:
PR tree-opt/66768
* tree-ssa-address.c (create_mem_ref_raw): U
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66768
Georg-Johann Lay changed:
What|Removed |Added
Keywords||addr-space
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66768
--- Comment #9 from rguenther at suse dot de ---
On Tue, 7 Jul 2015, amker at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66768
>
> --- Comment #8 from amker at gcc dot gnu.org ---
> So address space info is kept and c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66768
--- Comment #8 from amker at gcc dot gnu.org ---
So address space info is kept and checked in base object's type of MEM_REF. As
in function expand_expr_real_1:
case TARGET_MEM_REF:
{
addr_space_t as
= TYPE_ADDR_SPACE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66768
--- Comment #7 from amker at gcc dot gnu.org ---
(In reply to Richard Biener from comment #6)
> IVOPTs seems to carry address-space info on 'type' here (in fact if I amend
> tree dumping with address-space dumping on memory references I fail to ge
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66768
Richard Biener changed:
What|Removed |Added
Keywords||wrong-code
Target|
