Bug 22413 - [telepathy-gabble 0.7.29] gcc 4.4 -O2 strict-aliasing warning
Summary: [telepathy-gabble 0.7.29] gcc 4.4 -O2 strict-aliasing warning
Status: RESOLVED DUPLICATE of bug 23685
Alias: None
Product: Telepathy
Classification: Unclassified
Component: gabble (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-22 06:20 UTC by Ionut Biru
Modified: 2009-09-14 12:23 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
compilation log (15.02 KB, application/octet-stream)
2009-06-22 06:20 UTC, Ionut Biru
Details

Description Ionut Biru 2009-06-22 06:20:44 UTC
Created attachment 27006 [details]
compilation log

my CFLAGS is -march=x86-64 -mtune=generic -O2 -pipe. is not x86_64 related and
is working if i add -fno-strict-aliasing.

asyncns.c: In function ‘asyncns_wait’:
asyncns.c:984: warning: dereferencing pointer ‘ai_resp’ does break strict-aliasing rules
asyncns.c:985: warning: dereferencing pointer ‘ai_resp’ does break strict-aliasing rules
asyncns.c:986: warning: dereferencing pointer ‘ai_resp’ does break strict-aliasing rules
asyncns.c:976: note: initialized from here
asyncns.c:1017: warning: dereferencing pointer ‘ni_resp’ does break strict-aliasing rules
asyncns.c:1018: warning: dereferencing pointer ‘ni_resp’ does break strict-aliasing rules
asyncns.c:1019: warning: dereferencing pointer ‘ni_resp’ does break strict-aliasing rules
asyncns.c:1021: warning: dereferencing pointer ‘ni_resp’ does break strict-aliasing rules
Comment 1 Simon McVittie 2009-08-24 13:13:17 UTC
Hopefully we can fix this by updating to a newer asyncns.

Could you please try the latest version of asyncns from its author, available from <http://0pointer.de/lennart/projects/libasyncns/>, and see whether that compiles without warnings? If it does, we'll just need to update to a newer version; if it doesn't, please report the bug to Lennart.
Comment 2 Simon McVittie 2009-09-14 12:23:31 UTC

*** This bug has been marked as a duplicate of bug 23685 ***


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.