Bug 316272

Summary:	dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
Product:	[Applications] akregator	Reporter:	jms <jms.gentoo>
Component:	metakit plugin	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	minor
Priority:	NOR
Version:	4.10.1
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description jms 2013-03-07 02:59:11 UTC

When building it got this message..

>>> Messages generated by process 4890 on 2013-03-06 20:05:14 VET for package kde-base/akregator-4.10.1:

QA: other
QA Notice: Package triggers severe warnings which indicate that it
           may exhibit random runtime failures.
/var/tmp/portage/kde-base/akregator-4.10.1/work/akregator-4.10.1/akregator/plugins/mk4storage/metakit/src/column.cpp:816:13: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
/var/tmp/portage/kde-base/akregator-4.10.1/work/akregator-4.10.1/akregator/plugins/mk4storage/metakit/src/column.cpp:823:13: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
/var/tmp/portage/kde-base/akregator-4.10.1/work/akregator-4.10.1/akregator/plugins/mk4storage/metakit/src/column.cpp:830:13: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
/var/tmp/portage/kde-base/akregator-4.10.1/work/akregator-4.10.1/akregator/plugins/mk4storage/metakit/src/column.cpp:837:13: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
/var/tmp/portage/kde-base/akregator-4.10.1/work/akregator-4.10.1/akregator/plugins/mk4storage/metakit/src/column.cpp:844:13: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
/var/tmp/portage/kde-base/akregator-4.10.1/work/akregator-4.10.1/akregator/plugins/mk4storage/metakit/src/column.cpp:856:13: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
/var/tmp/portage/kde-base/akregator-4.10.1/work/akregator-4.10.1/akregator/plugins/mk4storage/metakit/src/column.cpp:856:36: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
/var/tmp/portage/kde-base/akregator-4.10.1/work/akregator-4.10.1/akregator/plugins/mk4storage/metakit/src/column.cpp:872:13: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
/var/tmp/portage/kde-base/akregator-4.10.1/work/akregator-4.10.1/akregator/plugins/mk4storage/metakit/src/column.cpp:872:36: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
/var/tmp/portage/kde-base/akregator-4.10.1/work/akregator-4.10.1/akregator/plugins/mk4storage/metakit/src/column.cpp:1020:12: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
/var/tmp/portage/kde-base/akregator-4.10.1/work/akregator-4.10.1/akregator/plugins/mk4storage/metakit/src/persist.cpp:46:12: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
/var/tmp/portage/kde-base/akregator-4.10.1/work/akregator-4.10.1/akregator/plugins/mk4storage/metakit/src/persist.cpp:90:19: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
/var/tmp/portage/kde-base/akregator-4.10.1/work/akregator-4.10.1/akregator/plugins/mk4storage/metakit/src/viewx.cpp:776:40: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
Please do not file a Gentoo bug and instead report the above QA
issues directly to the upstream developers of this software.
Homepage: http://www.kde.org/

Comment 1 Denis Kurz 2016-09-24 19:38:06 UTC

This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of akregator (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.

Comment 2 Denis Kurz 2017-01-07 22:46:21 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.