This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Question about mem_set_list in propagate_block_info
- From: Diego Novillo <dnovillo at redhat dot com>
- To: Richard Henderson <rth at redhat dot com>
- Cc: fnf at intrinsity dot com, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: 04 Jun 2003 00:25:05 -0400
- Subject: Re: Question about mem_set_list in propagate_block_info
- Organization: Red Hat Canada
- References: <200306040045.h540jPdB009467@fred.ninemoons.com> <20030604041327.GK19452@redhat.com>
On Wed, 2003-06-04 at 00:13, Richard Henderson wrote:
> On Tue, Jun 03, 2003 at 05:45:25PM -0700, Fred Fish wrote:
> > (insn 11 10 13 0 0x4029aa40 (set (mem/f:V16SI (reg/f:SI 1 at) [3 S64 A512])
> > (reg:V16SI 210)) 355 {*movv16si_internal} (nil)
> > (nil))
> >
> > (insn 13 11 21 0 0x4029aa40 (set (reg/v:SI 211 [ m00 ])
> > (mem:SI (reg/f:SI 1 at) [4 S4 A32])) 188 {movsi_internal} (nil)
> > (nil))
>
> Look at the first number inside the []. This is the alias set number.
> In this case, 3 and 4 respectively. Since the numbers are different,
> the memories are not considered overlapping.
>
Wait, that doesn't follow. You can have different alias set numbers
that are conflicting.
Diego.