linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev 085 warnings
Date: Wed, 05 Apr 2006 19:03:15 +0000	[thread overview]
Message-ID: <20060405190315.GB21206@vrfy.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0604051110170.11179@yvahk01.tjqt.qr>

On Wed, Apr 05, 2006 at 11:10:40AM +0200, Jan Engelhardt wrote:
> I am currently compiling udev-085-14.src.rpm from the opensuse OSS-factory 
> tree on a 64-bit arch and get a lot of these warnings:
> 
> fat.c:325: warning: cast increases required alignment of target type
> 325:
>                 next = le32_to_cpu(*((uint32_t *) buf) & 0x0fffffff);
> 
> Will there be a proper fix or is this just another of these nice gcc 
> warnings that are superfluous?

GCC is correct warning about that, cause the Makefile asked for that
kind of warning. The buffer access is always aligned but the compiler
can't know that. To get rid of it, you would need to memcpy() the integer
in a variable or access it byte by byte and shift it to an integer
value. Removing -Wcast-align should be the easiest. :)

Kay


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&dat\x121642
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  reply	other threads:[~2006-04-05 19:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-05  9:10 udev 085 warnings Jan Engelhardt
2006-04-05 19:03 ` Kay Sievers [this message]
2006-04-06  0:30 ` Michael Buesch
2006-04-06  2:09 ` Kay Sievers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060405190315.GB21206@vrfy.org \
    --to=kay.sievers@vrfy.org \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).