public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tetsuyuki Kobayashi <koba@kmckk.co.jp>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: rmobile: Support build with gcc-4.6 or later
Date: Fri, 06 Jul 2012 17:04:16 +0900	[thread overview]
Message-ID: <4FF69C00.2010207@kmckk.co.jp> (raw)
In-Reply-To: <1341533207-17101-1-git-send-email-nobuhiro.iwamatsu.yj@renesas.com>

Hello, Iwamatsu-san

(2012/07/06 9:06), Nobuhiro Iwamatsu wrote:
> Latest rmobile code was tested by using old gcc (gcc-4.4).
> When we use gcc-4.6 (or later), the build is made, but does not work.
> This solves a problem not to work by add -march=armv5 to compiple option
> when we built in gcc-4.6 (or later).
> I tested by linaro's compiler version 2012.04-20120426.

Yes. I know recent gcc causes problem because of unaligned access.
There are 2 different proposals, but neither accepted.

[PATCH] arm: enable unaligned access on ARMv7
http://lists.denx.de/pipermail/u-boot/2012-June/125754.html

[PATCH] arm: armv7: add compile option -mno-unaligned-access if available
http://lists.denx.de/pipermail/u-boot/2012-July/127260.html

This patch is the third one.

> --- a/arch/arm/cpu/armv7/rmobile/lowlevel_init.S
> +++ b/arch/arm/cpu/armv7/rmobile/lowlevel_init.S
> @@ -49,8 +49,6 @@ wait_interrupt:
>   	str     r2, [r1]
>   
>   wait_loop:
> -	wfi
> -
>   	ldr		r2, [r1, #0xC]
>   	str		r2, [r1, #0x10]

I know "wfi" instruction causes compile error in -march=armv5.
Without this, it works but not so good because 2nd CPU wastes cycles.

I wonder, is there any cheat such as ".word 0x...." (putting instruction code directly)
or something.

  reply	other threads:[~2012-07-06  8:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-06  0:06 [U-Boot] [PATCH] arm: rmobile: Support build with gcc-4.6 or later Nobuhiro Iwamatsu
2012-07-06  8:04 ` Tetsuyuki Kobayashi [this message]
2012-07-19 22:30   ` Nobuhiro Iwamatsu

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=4FF69C00.2010207@kmckk.co.jp \
    --to=koba@kmckk.co.jp \
    --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