https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108187
--- Comment #3 from Ilya Maximets ---
(In reply to Ilya Maximets from comment #2)
> (In reply to Richard Biener from comment #1)
> > Well, between the store to ->source and the read from it is the call
> > to dp_packet_use_afxdp which gets &xpac
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108187
--- Comment #2 from Ilya Maximets ---
(In reply to Richard Biener from comment #1)
> Well, between the store to ->source and the read from it is the call
> to dp_packet_use_afxdp which gets &xpacket->packet as argument and thus
> needs to be tre
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108187
Bug ID: 108187
Summary: False positive -Wfree-nonheap-object on impossible
path with -O1
Product: gcc
Version: 12.2.1
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103964
--- Comment #12 from Ilya Maximets ---
> (In reply to Ilya Maximets from comment #7)
> > One thing that is not clear to me is if the following code has an UB or not:
> >
> > struct member* pos;
> > struct ovs_list start;
> >
> > po
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103964
--- Comment #10 from Ilya Maximets ---
(In reply to Jakub Jelinek from comment #9)
> (In reply to Ilya Maximets from comment #7)
> > (In reply to Jakub Jelinek from comment #6)
> > > What is the reason why OVS (and kernel) doesn't use 2 variable
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103964
--- Comment #7 from Ilya Maximets ---
(In reply to Jakub Jelinek from comment #6)
> What is the reason why OVS (and kernel) doesn't use 2 variables, one for the
> iterator that is a pointer to the prev/next structure only and one assigned
> e.g.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103964
--- Comment #5 from Ilya Maximets ---
(In reply to Richard Biener from comment #4)
> the IVOPTs reference is likely due to the fact that while IVOPTs uses
> uintptrs to create the base pointer the TARGET_MEM_REF contained arithmetic
> itself is
