Re: BUG #8588: Need work arounds for Apple unaligned access

From: Jeffrey Walton <noloader(at)gmail(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #8588: Need work arounds for Apple unaligned access
Date: 2013-11-12 23:10:28
Message-ID: CAH8yC8ks=mtjz=nVd0TL-Fw=fEzdyRTbn34Y8UPP=QW_pqdEZg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Nov 12, 2013 at 5:00 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> On 11/11/13, 4:04 PM, Jeffrey Walton wrote:
>> Did Apple supply any patches or file any bug reports? Or is Apple
>> omitting acceptance checks?
>
> The clang sanitizers are clearly still experimental. It's worth
> investigating the issues they point out, but they are not used in
> production builds.
I can only speak of Address Sanitizer (-fsanitize=address) and
Undefined Behavior (-fsanitize=undefined) because I use them often. To
date (and for me), every finding produced by them has been accurate.
They don't miss with false positives.

I'm trying to work through an address sanitizer finding now. This may
be the first false positive I encounter. Or it might be a valid
finding. I need to learn more since I've never seen it before.

For completeness, I don't use -fsanitize=memory or -fsanitize=thread.
I think they are closer to what your are talking about (experimental).
Valgrind and Helgrind are usually pretty good in this area (sans
spurious noise modulo suppression rules).

Jeff

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Jeffrey Walton 2013-11-13 00:58:31 Clang 3.3 findings and Illegal Shifts
Previous Message Tom Lane 2013-11-12 22:06:58 Re: Re: BUG #8448: looping through query results exits at 10th step under some conditions