From mboxrd@z Thu Jan  1 00:00:00 1970
From: Dirk Behme <dirk.behme@googlemail.com>
Date: Tue, 21 Dec 2010 21:04:54 +0100
Subject: [U-Boot] [RFC PATCH v2] ARM: Avoid compiler optimization for
 usages of readb, writeb and friends.
In-Reply-To: <20101221195215.DB74C126EB1A@gemini.denx.de>
References: <1292711230-3234-1-git-send-email-holler@ahsoftware.de>	<4D0DDCEF.2040806@ahsoftware.de>	<AANLkTik3-EL1VDpn1L5YY01Amv6VzSEKduxU=R9nPJrx@mail.gmail.com>	<4D0E643A.9040001@ahsoftware.de>	<AANLkTinWsOgqOXyLk+nN0AB8Kw33txG9Ot3Ji7Ckd-SO@mail.gmail.com>	<4D0EA9BB.4050002@ahsoftware.de>	<AANLkTikxZM3G2HTXhf1BNy28zkiBdJ-=Q4RWSv13ZQcS@mail.gmail.com>	<AANLkTiksYKRt7DMsVwqA--WAachCfJuC65v-XgotLLyS@mail.gmail.com>	<4D0F8E75.2010107@ahsoftware.de>	<AANLkTinXN-as+0-k9HZmh571vZPdzOh8hmq3zX4XSQta@mail.gmail.com>	<AANLkTinMK=gzYgyUTjkCg2y1g9YuRAu_P-DS0GARrfPR@mail.gmail.com>	<4D105324.2080201@googlemail.com>
	<4D105583.8070703@free.fr>	<4D1066CD.2040409@googlemail.com>	<AANLkTikN-02Eay6u90DMKHuL8uvy7e0VLFSebxDsdoEo@mail.gmail.com>	<4D1083B4.2060704@free.fr>	<20101221105303.4E3EDB715C@gemini.denx.de>	<4D109F06.1040109@ahsoftware.de>
	<4D10A2E7.6050302@free.fr>	<4D10ABDE.7010303@ahsoftware.de>
	<4D10BAB2.9080300@free.fr>
	<20101221195215.DB74C126EB1A@gemini.denx.de>
Message-ID: <4D110866.6020209@googlemail.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On 21.12.2010 20:52, Wolfgang Denk wrote:
> Dear Albert&  friends,
>
> what is your opinion?  Should we include the memory barrier patch into
> the upcoming release (and eventually delay it for further testing), or
> release as is and solve this issue in the next release?
>
> I tend to leave it as is, as I expect that most people will disappear
> in the next few days for holidays, so no much testing will be done
> anyway, and we then can solve this with less pressure in the next
> release - but I'm not really sure if this is a good idea?

I somehow tend to leave it as is, too.

We have issues with some recent compilers. For these we found a fix 
using the io.h somehow the same way the Linux kernel does. But this 
introduces new issues for us, we haven't found a proper fix yet 
(except changing the code to the 'old' io.h style). But we don't know 
where we might have this issue additionally, yet.

I would like to talk with some tool chain guys about this, too.

Could we add a readme or a note somewhere about the issues with the 
recent tool chains in this release?

Best regards

Dirk