Date: Tue, 18 Sep 2012 09:00:38 -1000 (HST) From: Jeff Roberson <jroberson@jroberson.net> To: Poul-Henning Kamp <phk@phk.freebsd.dk> Cc: Konstantin Belousov <kostikbel@gmail.com>, attilio@freebsd.org, freebsd-arch@freebsd.org, arch@freebsd.org Subject: Re: Aliasing issue with TAILQ on ppc64 ? Message-ID: <alpine.BSF.2.00.1209180858190.47770@desktop> In-Reply-To: <22851.1347992668@critter.freebsd.dk> References: <22851.1347992668@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 18 Sep 2012, Poul-Henning Kamp wrote:
> In message <201209181359.37965.jhb@freebsd.org>, John Baldwin writes:
>> On Tuesday, September 18, 2012 1:03:21 pm Poul-Henning Kamp wrote:
>
>> Did you have -fno-strict-aliasing enabled in CFLAGS for your PPC64 build
>> (assuming you had built with -O2 or higher)?
>
> I tried that, but it did not seem to make a difference.
If you compile at low optimization levels I assume it goes away?
Can you place asm volatile ("" ::: "memory"); between the two tailq macros
with the same optimization level? This should prevent gcc from caching
anything in registers regardless of the optimization level and would tell
us if it's doing something bad.
Thanks,
Jeff
>
> --
> Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
> phk@FreeBSD.ORG | TCP/IP since RFC 956
> FreeBSD committer | BSD since 4.3-tahoe
> Never attribute to malice what can adequately be explained by incompetence.
> _______________________________________________
> freebsd-arch@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-arch
> To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1209180858190.47770>