After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 141066 - queryimmodules.c: query_module - warning: dereferencing type-punned pointer will break strict-aliasing rules
queryimmodules.c: query_module - warning: dereferencing type-punned pointer w...
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: Other
2.8.x
Other Linux
: Normal normal
: Small fix
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2004-04-25 13:00 UTC by Chris Sherlock
Modified: 2013-02-11 05:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Attachments
Proposed patch (1.68 KB, patch)
2004-04-25 13:01 UTC, Chris Sherlock
none Details | Review

Description Chris Sherlock 2004-04-25 13:00:18 UTC
Same reason as for bug reports:

* Bug 140346: libmoduletestplugin_a.c gives type-punned warning when compiling
glibc-2.2.3
* Bug 141010: When compiling queryloaders.c gcc generates warning that
dereferencing type-punned pointer breaks strict-aliasing
* Bug 141020: gtkmain.c: multiple warnings about deferencing type-punned pointer
breaks strict aliasing rules
* Bug 141024: gtkselection.c: gtk_selection_convert - warning about deferencing
type-punned pointer breaking strict aliasing rules
* Bug 141027: gtktipsquery.c: gtk_tips_query_event - warning about deferencing
type-punned pointer breaks strict aliasing rules
* Bug 141030: gtkwidget.c: gtk_widget_reparent_subwindows - warning about
deferencing type-punned pointer breaking strict aliasing rules
Comment 1 Chris Sherlock 2004-04-25 13:01:02 UTC
Created attachment 27069 [details] [review]
Proposed patch
Comment 2 Christian Kirbach 2006-06-04 13:49:33 UTC
patch still applies and fixes the warnings
Comment 3 Behdad Esfahbod 2006-06-09 22:00:59 UTC
Note that these kind of patches just hide the warning, they don't actually fix the problem.
Comment 4 Behdad Esfahbod 2006-06-09 22:01:39 UTC
The proper fix is something like what's in bug 335853
Comment 5 Matthias Clasen 2013-02-11 05:16:41 UTC
closing old bugs, no need to keep bugs about compiler warnings open for decades