On Mon, Feb 22, 2010 at 1:45 PM, Marc Lehmann <schm...@schmorp.de> wrote: > On Mon, Feb 22, 2010 at 12:59:08PM -0600, Brandon Black <blbl...@gmail.com> > wrote: >> On Sun, Feb 21, 2010 at 3:39 AM, Marc Lehmann <schm...@schmorp.de> wrote: >> > On Sat, Feb 20, 2010 at 09:41:35AM -0600, Brandon Black >> > <blbl...@gmail.com> wrote: >> >> I've seen this strict-aliasing issues with libev + gcc 4.4 as well. I >> > Facts please... >> >> I wasn't asserting that there was an aliasing issue in libev. I was > > Well, you asserted a "strict-aliasing issue", which to me sounds a lot > like an aliasing issue... > >> asserting that there is a strict aliasing warning with gcc + libev, > > That's not what you asserted, but maybe what you meant. You even quoted > it... [...] > Can we settle this please, or _finally_ bring some evidence?
You're arguing with the wrong person. I didn't submit the patch, and I have never once asserted that there was a problem with the libev code with regards to aliasing. I just find these warnings confusing, as do many people, and I'm trying to find clarification on them. -- Brandon _______________________________________________ libev mailing list libev@lists.schmorp.de http://lists.schmorp.de/cgi-bin/mailman/listinfo/libev
