From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3] ARM: Avoid compiler optimization for usages of readb, writeb and friends.
Date: Wed, 22 Dec 2010 15:50:02 +0100 [thread overview]
Message-ID: <4D12101A.4030807@googlemail.com> (raw)
In-Reply-To: <1293015862-3678-1-git-send-email-holler@ahsoftware.de>
On 22.12.2010 12:04, Alexander Holler wrote:
> gcc 4.5.1 seems to ignore (at least some) volatile definitions,
> avoid that as done in the kernel.
>
> Reading C99 6.7.3 8 and the comment 114) there, I think it is a bug of that
> gcc version to ignore the volatile type qualifier used e.g. in __arch_getl().
> Anyway, using a definition as in the kernel headers avoids such optimizations when
> gcc 4.5.1 is used.
>
> Maybe the headers as used in the current linux-kernel should be used,
> but to avoid large changes, I've just added a small change to the current headers.
>
> I haven't add the definitions which are using a memory barrier because I haven't found
> a place in the kernel where they were actually enabled (CONFIG_ARM_DMA_MEM_BUFFERABLE).
>
> Signed-off-by: Alexander Holler<holler@ahsoftware.de>
This patch seems to be the same as the proposal from Wolfgang
http://lists.denx.de/pipermail/u-boot/2010-December/084122.html
So we shouldn't drop his
Signed-off-by: Wolfgang Denk <wd@denx.de>
Besides of this
Acked-by: Dirk Behme <dirk.behme@googlemail.com>
Thanks
Dirk
> ---
> arch/arm/include/asm/io.h | 20 ++++++++++++++------
> 1 files changed, 14 insertions(+), 6 deletions(-)
>
> diff --git a/arch/arm/include/asm/io.h b/arch/arm/include/asm/io.h
> index ff1518e..068ed17 100644
> --- a/arch/arm/include/asm/io.h
> +++ b/arch/arm/include/asm/io.h
> @@ -125,13 +125,21 @@ extern inline void __raw_readsl(unsigned int addr, void *data, int longlen)
> #define __raw_readw(a) __arch_getw(a)
> #define __raw_readl(a) __arch_getl(a)
>
> -#define writeb(v,a) __arch_putb(v,a)
> -#define writew(v,a) __arch_putw(v,a)
> -#define writel(v,a) __arch_putl(v,a)
> +/*
> + * TODO: The kernel offers some more advanced versions of barriers, it might
> + * have some advantages to use them instead of the simple one here.
> + */
> +#define dmb() __asm__ __volatile__ ("" : : : "memory")
> +#define __iormb() dmb()
> +#define __iowmb() dmb()
> +
> +#define writeb(v,c) do { __iowmb(); __arch_putb(v,c); } while (0)
> +#define writew(v,c) do { __iowmb(); __arch_putw(v,c); } while (0)
> +#define writel(v,c) do { __iowmb(); __arch_putl(v,c); } while (0)
>
> -#define readb(a) __arch_getb(a)
> -#define readw(a) __arch_getw(a)
> -#define readl(a) __arch_getl(a)
> +#define readb(c) ({ u8 __v = __arch_getb(c); __iormb(); __v; })
> +#define readw(c) ({ u16 __v = __arch_getw(c); __iormb(); __v; })
> +#define readl(c) ({ u32 __v = __arch_getl(c); __iormb(); __v; })
>
> /*
> * The compiler seems to be incapable of optimising constants
next prev parent reply other threads:[~2010-12-22 14:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-22 11:04 [U-Boot] [PATCH v3] ARM: Avoid compiler optimization for usages of readb, writeb and friends Alexander Holler
2010-12-22 14:50 ` Dirk Behme [this message]
2010-12-22 15:07 ` Alexander Holler
2011-01-01 12:04 ` Dirk Behme
2011-01-01 17:52 ` Alexander Holler
2011-01-01 18:25 ` Dirk Behme
2011-01-01 18:47 ` Alexander Holler
2011-01-01 19:21 ` Dirk Behme
2011-01-02 12:43 ` Alexander Holler
2011-01-02 13:29 ` Dirk Behme
2011-01-02 21:00 ` Alexander Holler
2011-01-10 14:53 ` Alexander Holler
2011-01-10 15:05 ` Wolfgang Denk
2011-01-11 3:53 ` Alexander Holler
2011-01-09 22:25 ` Wolfgang Denk
2011-01-10 16:13 ` Dirk Behme
2011-01-17 21:59 ` Wolfgang Denk
2011-01-09 22:19 ` [U-Boot] [PATCH v4] ARM: Avoid compiler optimization for " Wolfgang Denk
2011-01-12 15:17 ` Thomas Weber
2011-01-12 15:39 ` Alexander Holler
2011-01-12 16:40 ` Wolfgang Denk
2011-01-12 16:49 ` Alexander Holler
2011-01-15 13:13 ` Albert ARIBAUD
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=4D12101A.4030807@googlemail.com \
--to=dirk.behme@googlemail.com \
--cc=u-boot@lists.denx.de \
/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