linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin <m_btrfs@ml1.co.uk>
To: linux-btrfs@vger.kernel.org
Subject: Re: progs integration branch moved to master (new default leafsize)
Date: Fri, 22 Nov 2013 19:50:17 +0000	[thread overview]
Message-ID: <l6oche$7sa$1@ger.gmane.org> (raw)
In-Reply-To: <20131122134038.5312.42200@localhost.localdomain>

On 22/11/13 13:40, Chris Mason wrote:
> Quoting Martin (2013-11-22 04:03:41)

>>  * QA Notice: Package triggers severe warnings which indicate that it
>>  *            may exhibit random runtime failures.
>>  * disk-io.c:91:5: warning: dereferencing type-punned pointer will break
>> strict-aliasing rules [-Wstrict-aliasing]
>>  * volumes.c:1930:5: warning: dereferencing type-punned pointer will
>> break strict-aliasing rules [-Wstrict-aliasing]
>>  * volumes.c:1931:6: warning: dereferencing type-punned pointer will
>> break strict-aliasing rules [-Wstrict-aliasing]
> 
> Does gentoo modify the optimizations from the Makefile?  We actually
> have many strict-aliasing warnings, but I didn't think they came up
> until -O2.

For that system, I have -Os set in the Gentoo "make.conf".


> At any rate, I'm adding -fno-strict-aliasing just to be sure.

Good to catch to avoid unexpectedness,


Regards,
Martin




  reply	other threads:[~2013-11-22 19:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-08 22:01 progs integration branch moved to master (new default leafsize) Chris Mason
2013-11-08 23:53 ` Martin
2013-11-21 23:37   ` Chris Mason
2013-11-22  9:03     ` Martin
2013-11-22 13:40       ` Chris Mason
2013-11-22 19:50         ` Martin [this message]
2013-11-22 19:57           ` Chris Mason
2013-11-23  0:02             ` Martin
2013-11-22 22:05         ` Duncan
2013-11-14 12:41 ` David Sterba
  -- strict thread matches above, loose matches on Subject: below --
2013-11-14 17:28 Chris Mason

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='l6oche$7sa$1@ger.gmane.org' \
    --to=m_btrfs@ml1.co.uk \
    --cc=linux-btrfs@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).