linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Soltys <soltys@ziu.info>
To: David Brown <david@westcontrol.com>
Cc: David Brown <david.brown@hesbynett.no>,
	linux-raid@vger.kernel.org, Jes.Sorensen@redhat.com,
	dledford@redhat.com
Subject: Re: [PATCH 1/1] Work around gcc-4.7's strict aliasing checks
Date: Fri, 13 Jan 2012 15:21:09 +0100	[thread overview]
Message-ID: <4F103DD5.4090402@ziu.info> (raw)
In-Reply-To: <4F1021A3.6020203@westcontrol.com>

On 13.01.2012 13:20, David Brown wrote:
>>
>> OTOH: __attribute__((__may_alias__)) should(?) always give consistent
>> (expected) results with type definitions that are used as aliases.
>> Maybe it would be better to go by this route.
>
> I couldn't find that attribute in the gcc manual.

http://gcc.gnu.org/onlinedocs/gcc/Type-Attributes.html#Type-Attributes

Near the bottom of the page.

  reply	other threads:[~2012-01-13 14:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-05 11:16 [PATCH 0/1] gcc-4.7 build fix Jes.Sorensen
2012-01-05 11:16 ` [PATCH 1/1] Work around gcc-4.7's strict aliasing checks Jes.Sorensen
2012-01-11 23:43   ` NeilBrown
2012-01-12  7:14     ` David Brown
2012-01-12 13:45       ` Michal Soltys
2012-01-13 12:20         ` David Brown
2012-01-13 14:21           ` Michal Soltys [this message]
2012-01-13 17:48             ` David Brown
2012-01-12  9:24     ` Jes Sorensen
2012-01-22  0:49     ` Michal Soltys
2012-01-22  0:49       ` [PATCH] compile cleanly with -Wstrict-aliasing=1 Michal Soltys
2012-01-23 12:50       ` [PATCH 1/1] Work around gcc-4.7's strict aliasing checks Jes Sorensen
2012-01-24  0:59         ` Michal Soltys
2012-01-24  9:18           ` David Brown

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=4F103DD5.4090402@ziu.info \
    --to=soltys@ziu.info \
    --cc=Jes.Sorensen@redhat.com \
    --cc=david.brown@hesbynett.no \
    --cc=david@westcontrol.com \
    --cc=dledford@redhat.com \
    --cc=linux-raid@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).