Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: khc@pm.waw.pl (Krzysztof Halasa)
To: linux-arm-kernel@lists.infradead.org
Subject: FYI GCC 4.6.x miscompiles the kernel
Date: Sun, 14 Aug 2011 18:05:55 +0200	[thread overview]
Message-ID: <m31uwo6krg.fsf_-_@intrepid.localdomain> (raw)
In-Reply-To: <201108140327.06726.marek.vasut@gmail.com> (Marek Vasut's message of "Sun, 14 Aug 2011 03:27:05 +0200")

Correction: this bug isn't ARM-specific.

Marek Vasut <marek.vasut@gmail.com> writes:

>> Current gcc-4.6.x SVN, ARMEB EABI.
>
> Shouldn't this go to GCC ML too ?

Nope, I put it in bugzilla.

>> unsigned var[2];
>>
>> void test(int arg)
>> {
>>         unsigned v = *(volatile unsigned *)(&var[arg]);
>>         *(volatile unsigned *)(&var[arg]) = v;
>> }
>>
>> Disassembly of section .text:
>>
>> 00000000 <test>:
>>    0:   e12fff1e        bx      lr

On x86-64:
0000000000000000 <test>:
   0:   f3 c3                   repz retq
-- 
Krzysztof Halasa

      reply	other threads:[~2011-08-14 16:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-13 23:10 FYI ARM GCC 4.6.x miscompiles the kernel Krzysztof Halasa
2011-08-14  1:27 ` Marek Vasut
2011-08-14 16:05   ` Krzysztof Halasa [this message]

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=m31uwo6krg.fsf_-_@intrepid.localdomain \
    --to=khc@pm.waw.pl \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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