Bug 22411

Summary: [libnice 0.0.8] gcc 4.4 -O2 break sha1 algorithm strict-aliasing warning.
Product: nice Reporter: Ionut Biru <biru.ionut>
Component: GeneralAssignee: Youness Alaoui <youness.alaoui>
Status: CLOSED FIXED QA Contact: Dafydd Harries <dafydd.harries>
Severity: major    
Priority: high    
Version: unspecified   
Hardware: Other   
OS: All   
URL: http://bugs.archlinux.org/task/15189
Whiteboard:
i915 platform: i915 features:
Attachments: compilation log

Description Ionut Biru 2009-06-22 06:10:01 UTC
Created attachment 27004 [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.
this makes tests 3 out of 5 tests failing.
i tested with gcc 4.3 on debian unstable which have -g -O2 and is working without any issue and i'm suspecting that gcc4.4 has strict-aliasing

sha1.c: In function ‘SHA1Transform’:
sha1.c:180: warning: dereferencing pointer ‘block’ does break strict-aliasing rules
sha1.c:180: warning: dereferencing pointer ‘block’ does break strict-aliasing rules
sha1.c:180: warning: dereferencing pointer ‘block’ does break strict-aliasing rules
sha1.c:180: warning: dereferencing pointer ‘block’ does break strict-aliasing rules
sha1.c:179: warning: dereferencing pointer ‘block’ does break strict-aliasing rules
sha1.c:179: warning: dereferencing pointer ‘block’ does break strict-aliasing rules

this is just a half of warnings. i'm attaching compilation log. feel free to ask me anything related to my system.
Comment 1 Simon McVittie 2010-03-18 06:17:30 UTC
The branch from Bug #27164 adds -fno-strict-aliasing. Youness, could you fast-track that in ahead of the rest of the branch?
Comment 2 Youness Alaoui 2010-03-18 10:40:31 UTC
This is the same bug as : http://bugs.archlinux.org/task/15189
and it was already fixed on July 2nd 2009 and the fix has already been released in version 0.0.9 back in July.
Closing bug.

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.