This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug tree-optimization/31358] IV-OPTs produces a weird MEM_REF



------- Comment #1 from rakdver at gcc dot gnu dot org  2007-03-26 10:17 -------
(In reply to comment #0)
> For:
> int *f(int *a, int b, int c)
> {
>   int i;
>   a --;
>   *a = 1;
>   for (i = 0;i<b;i+=c)
>     (a[i]) = 0;
>   return a;
> }
> ----------------CUT----------------
> I get in the final_cleanup:
>   MEM[index: ivtmp.35, offset: 4294967292] = 0;
> 
> 
> And I noticed that ivtmp.29 is of type "long unsigned int" which seems wrong as
> it is actually the pointer.

no, this is OK (whether it is a good design choice is another thing, I will
think about that).


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31358


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]