GNOME Bugzilla – Bug 651575
dereferencing type-punned pointer will break strict-aliasing rules
Last modified: 2011-06-01 08:05:05 UTC
When compiling from Jhbuild (gnome3.2 moduleset), after encountering and fixing #651514, I get the following errors : (if I use the patch in comment 1) gstelementfactory.c: In function ‘gst_element_factory_create’: gstelementfactory.c:397:8: error: dereferencing type-punned pointer will break strict-aliasing rules gstelementfactory.c:397:8: error: dereferencing type-punned pointer will break strict-aliasing rules And if I put () around the macro I get the same erros in gstatomicqueue.c: gstatomicqueue.c: In function ‘add_to_free_list’: gstatomicqueue.c:115:13: error: dereferencing type-punned pointer will break strict-aliasing rules gstatomicqueue.c:115:13: error: dereferencing type-punned pointer will break strict-aliasing rules gstatomicqueue.c: In function ‘clear_free_list’: gstatomicqueue.c:129:13: error: dereferencing type-punned pointer will break strict-aliasing rules gstatomicqueue.c:129:13: error: dereferencing type-punned pointer will break strict-aliasing rules gstatomicqueue.c: In function ‘gst_atomic_queue_peek’: gstatomicqueue.c:250:10: error: dereferencing type-punned pointer will break strict-aliasing rules gstatomicqueue.c:250:10: error: dereferencing type-punned pointer will break strict-aliasing rules gstatomicqueue.c: In function ‘gst_atomic_queue_pop’: gstatomicqueue.c:307:12: error: dereferencing type-punned pointer will break strict-aliasing rules gstatomicqueue.c:307:12: error: dereferencing type-punned pointer will break strict-aliasing rules gstatomicqueue.c: In function ‘gst_atomic_queue_push’: gstatomicqueue.c:365:12: error: dereferencing type-punned pointer will break strict-aliasing rules gstatomicqueue.c:365:12: error: dereferencing type-punned pointer will break strict-aliasing rules make[4]: *** [libgstreamer_0.10_la-gstatomicqueue.lo] Erreur 1
Why did you file a duplicate bug referencing the one you're duplicating?
Because I saw a different error message and didn't understood the technical implications of the other bug so I assumed it was a different issue. Sorry about that