[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#120223: marked as done (libc6-dev: Warning on ARM with -Wcast-align)

Your message dated Thu, 27 Mar 2003 18:56:57 +0900
with message-id <804r5pi13q.wl@oris.opensource.jp>
and subject line Bug#120223: libc6-dev: Warning on ARM with -Wcast-align
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

Received: (at submit) by bugs.debian.org; 19 Nov 2001 16:59:32 +0000
>From peter@chocky.org Mon Nov 19 10:59:32 2001
Return-path: <peter@chocky.org>
Received: from pc2-camb3-0-cust6.cam.cable.ntl.com (bug) [] 
	by master.debian.org with esmtp (Exim 3.12 1 (Debian))
	id 165rlb-00004w-00; Mon, 19 Nov 2001 10:59:31 -0600
Received: from peter by bug with local (Exim 3.32 #1 (Debian))
	id 165rlc-0002Lh-00; Mon, 19 Nov 2001 16:59:32 +0000
From: Peter Naulls <peter@chocky.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: libc6-dev: Warning on ARM with -Wcast-align
X-Reportbug-Version: 1.36
X-Mailer: reportbug 1.36
Date: Mon, 19 Nov 2001 16:59:31 +0000
Message-Id: <E165rlc-0002Lh-00@bug>
Delivered-To: submit@bugs.debian.org

Package: libc6-dev
Version: 2.2.4-6
Severity: normal

When using the warning -Wcast-align with GCC, and causing bits/socket.h to be included,
a warning is caused on ARM platforms:

In file included from /usr/include/netinet/in.h:212,
                 from /usr/include/netdb.h:28,
                 from netunix.c:18:
/usr/include/bits/socket.h: In function `__cmsg_nxthdr':
/usr/include/bits/socket.h:271: warning: cast increases required alignment of target type

This probably also occurs on other platforms where pointers for 32-bit values must be
32-bit aligned to be sensible (not x86).

This can probably be worked around with an intervening (void *) cast on line 270.


-- System Information
Debian Release: testing/unstable
Architecture: arm
Kernel: Linux bug 2.4.3-pre7-rmk2 #1 Mon May 14 10:18:42 BST 2001 armv4l

Versions of packages libc6-dev depends on:
ii  libc6                         2.2.4-6    GNU C Library: Shared libraries an

Received: (at 120223-done) by bugs.debian.org; 27 Mar 2003 09:56:59 +0000
>From gotom@debian.or.jp Thu Mar 27 03:56:58 2003
Return-path: <gotom@debian.or.jp>
Received: from oris.opensource.jp (oris.opensource.gr.jp) [] (postfix)
	by master.debian.org with esmtp (Exim 3.12 1 (Debian))
	id 18yU82-00040Y-00; Thu, 27 Mar 2003 03:56:58 -0600
Received: from oris.opensource.jp (oris.opensource.jp [])
	by oris.opensource.gr.jp (Postfix) with ESMTP
	id 4FFE5C33C7; Thu, 27 Mar 2003 18:56:57 +0900 (JST)
Date: Thu, 27 Mar 2003 18:56:57 +0900
Message-ID: <804r5pi13q.wl@oris.opensource.jp>
From: GOTO Masanori <gotom@debian.or.jp>
To: 120223-done@bugs.debian.org
Cc: Philip Blundell <pb@nexus.co.uk>
Subject: Re: Bug#120223: libc6-dev: Warning on ARM with -Wcast-align
In-Reply-To: <1043146218.25984.13.camel@mill.nexus.co.uk>
References: <1043146218.25984.13.camel@mill.nexus.co.uk>
User-Agent: Wanderlust/2.9.9 (Unchained Melody) SEMI/1.14.3 (Ushinoya)
 FLIM/1.14.3 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.2
 (i386-debian-linux-gnu) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Delivered-To: 120223-done@bugs.debian.org
X-Spam-Status: No, hits=-1.8 required=4.0

At 21 Jan 2003 10:50:18 +0000,
Philip Blundell wrote:
> I wasn't able to reproduce this failure with glibc 2.3 on ARM. 
> Submitter, is it still happening for you?  If so, I think we will need a
> test case to demonstrate the problem.

I also can't reproduce this problem on arm glibc 2.3.1.
There is no reply - and I think this bug is already fixed.
Now I close this bug.

-- gotom

Reply to: