This is the mail archive of the gcc@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]

Re: Documentation for loop infrastructure


Thank you, the documentation looks good.

Ira Rosen wrote:
> 
> @item @code{first_location_in_loop}: Provides information about the first
> location accessed by the data reference in the loop and about the access
> function used to represent evolution relative to this location. This data
> is used to support pointers, and is not used for arrays (for which we
> have base objects). Pointer accesses are represented as a one-dimensional
> access that starts from the first location accessed in the loop. For
> example:
> 
> @smallexample
>       for i
>          for j
>           *((int *)p + i + j) = a[i][j];
> @end smallexample
> 
> The access function of the pointer access is @code{@{0, + 4B@}_2} relative

It is probably better to include the loop indexes in the example, and
modify the syntax of the scev for making it more explicit, like:

@smallexample
      for1 i
         for2 j
          *((int *)p + i + j) = a[i][j];
@end smallexample

and the access function becomes: @code{@{0, + 4B@}_for2}


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