[gstreamer-bugs] [Bug 316079] MinGW compilation: G_LOCK and G_UNLOCK break strict-aliasing

[bugzilla-daemon at bugzilla.gnome.org]

Do not reply to this email.  You can add comments to this bug at
 http://bugzilla.gnome.org/show_bug.cgi?id=316079
 GStreamer | gstreamer (core) | Ver: HEAD CVS





------- Additional Comments From Michael Smith  2005-09-13 14:16 -------
I've encountered a number of cases where gcc4 badly miscompiles things if you
ignore this warning, for what it's worth - the new optimisation infrastructure
is much more agressive and relies heavily on the aliasing information. So fixing
this sort of issue is generally pretty important.

However, this doesn't seem to be triggering for other people, so there's clearly
something different. Does the win32 version of glib do funny/weird stuff with
the glib mutex definitions? It's more or less impossible to figure out what the
mess of evilly nested macros in the glib header files is actually doing here. 

Anyway, this looks more like a glib issue to me than a gstreamer one - our usage
of these G_LOCK macros looks fine. As a temporary workaround, you can, of
course, disable -Werror for this file.





------- You are receiving this mail because: -------
You are the assignee for the bug.
You are the QA contact for the bug.