https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64815
Terry Guo changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64815
--- Comment #5 from Terry Guo ---
(In reply to Andrew Pinski from comment #4)
> (In reply to Terry Guo from comment #2)
> > (In reply to Andrew Pinski from comment #1)
> > > I don't think you need to call volatile_refs_p on the notes part of the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64815
--- Comment #3 from Andrew Pinski ---
(In reply to Terry Guo from comment #2)
> (In reply to Andrew Pinski from comment #1)
> > I don't think you need to call volatile_refs_p on the notes part of the
> > instruciton.
>
> The volatile_refs_p work
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64815
--- Comment #3 from Andrew Pinski ---
(In reply to Terry Guo from comment #2)
> (In reply to Andrew Pinski from comment #1)
> > I don't think you need to call volatile_refs_p on the notes part of the
> > instruciton.
>
> The volatile_refs_p work
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64815
--- Comment #2 from Terry Guo ---
(In reply to Andrew Pinski from comment #1)
> I don't think you need to call volatile_refs_p on the notes part of the
> instruciton.
The volatile_refs_p works in a recursive way which makes itself to scan the
no
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64815
--- Comment #1 from Andrew Pinski ---
I don't think you need to call volatile_refs_p on the notes part of the
instruciton.
