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 571700 - Compilation warnings with gcc 4.4
Compilation warnings with gcc 4.4
Status: RESOLVED NOTABUG
Product: glibmm
Classification: Bindings
Component: build
2.19.x
Other Linux
: Normal minor
: ---
Assigned To: gtkmm-forge
gtkmm-forge
Depends on:
Blocks:
 
 
Reported: 2009-02-14 06:40 UTC by Denis Leroy
Modified: 2009-02-20 19:08 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Denis Leroy 2009-02-14 06:40:35 UTC 
We're seeing compile warnings with g++ 4.4, coming from refptr.h:

/usr/include/glibmm-2.4/glibmm/refptr.h: In constructor ‘WinMain::WinMain(bool)’:
/usr/include/glibmm-2.4/glibmm/refptr.h:172: warning: dereferencing pointer ‘<anonymous>’ does break strict-aliasing rules
/usr/include/glibmm-2.4/glibmm/refptr.h:285: warning: dereferencing pointer ‘<anonymous>’ does break strict-aliasing rules
/usr/lib/gcc/i386-redhat-linux/4.4.0/../../../../include/c++/4.4.0/bits/stl_list.h:219: note: initialized from here
/usr/include/glibmm-2.4/glibmm/refptr.h: In constructor ‘WinMain::WinMain(bool)’:
/usr/include/glibmm-2.4/glibmm/refptr.h:172: warning: dereferencing pointer ‘<anonymous>’ does break strict-aliasing rules
/usr/include/glibmm-2.4/glibmm/refptr.h:285: warning: dereferencing pointer ‘<anonymous>’ does break strict-aliasing rules
/usr/lib/gcc/i386-redhat-linux/4.4.0/../../../../include/c++/4.4.0/bits/stl_list.h:219: note: initialized from here
Comment 1 Murray Cumming 2009-02-15 22:05:39 UTC 
Can you show us what code is triggering this?
Is there some Fedora (that's what you mean by we, right?) bug URL for this that has more information?
Comment 2 Denis Leroy 2009-02-16 05:48:30 UTC 
Yes sorry, I should have given some more background info in the first place.

This occurs when compiling JD 2.2.0 :

https://bugzilla.redhat.com/show_bug.cgi?id=485407
Comment 3 Murray Cumming 2009-02-20 19:08:02 UTC 
According to the redhat bug report, this was fixed in g++.