From: matthew@mattleach.net (Matthew Leach)
To: linux-arm-kernel@lists.infradead.org
Subject: GCC 4.6.x miscompiling arm-linux?
Date: Mon, 10 Sep 2012 18:11:19 +0100 [thread overview]
Message-ID: <w51bohddcqw.fsf@mail.mattleach.net> (raw)
In-Reply-To: <20120910171654.1d4972b2@archvile> (David Jander's message of "Mon, 10 Sep 2012 17:16:54 +0200")
Hi David,
David Jander <david.jander@protonic.nl> writes:
> ...
> .text
> .align 2
> .global flexcan_chip_start
> .type flexcan_chip_start, %function
> flexcan_chip_start:
> @ args = 0, pretend = 0, frame = 0
> @ frame_needed = 0, uses_anonymous_args = 0
> @ link register save eliminated.
> mov r3, #0
> cmp r0, #9
> str r3, [r1, #0]
> ldrle r3, [r1, #4]
> mov r0, #0
> str r3, [r1, #4]
> bx lr
> .size flexcan_chip_start, .-flexcan_chip_start
> .ident "GCC: (OSELAS.Toolchain-2011.11.1) 4.6.2"
> .section .note.GNU-stack,"",%progbits
>
This does indeed look wrong. I had a go at compile your code snippet the
following assembly was produced:
.text
.align 2
.global flexcan_chip_start
.type flexcan_chip_start, %function
flexcan_chip_start:
@ Function supports interworking.
@ args = 0, pretend = 0, frame = 0
@ frame_needed = 0, uses_anonymous_args = 0
@ link register save eliminated.
cmp r0, #9
mov r3, #0
str r3, [r1, #0]
mov r0, #0
strgt r3, [r1, #4]
bx lr
.size flexcan_chip_start, .-flexcan_chip_start
.ident "GCC: (GNU) 4.3.3"
.section .note.GNU-stack,"",%progbits
I think this looks correct. Perhaps you could try the angstrom arm5te
toolchain and see if it's a toolchain issue?
http://www.angstrom-distribution.org/toolchains/angstrom-2011.03-i686-linux-armv5te-linux-gnueabi-toolchain-qte-4.6.3.tar.bz2
Thanks,
Matt
next prev parent reply other threads:[~2012-09-10 17:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 15:16 GCC 4.6.x miscompiling arm-linux? David Jander
2012-09-10 17:11 ` Matthew Leach [this message]
2012-09-11 7:27 ` David Jander
2012-09-11 7:54 ` David Jander
2012-09-11 8:11 ` Mikael Pettersson
2012-09-11 8:49 ` David Jander
2012-09-11 9:41 ` Mikael Pettersson
2012-09-11 10:37 ` David Jander
2012-09-11 11:35 ` Mikael Pettersson
2012-09-11 11:52 ` David Jander
2012-09-11 12:53 ` Mikael Pettersson
2012-09-11 13:43 ` David Jander
2012-09-11 14:10 ` Mikael Pettersson
2012-09-13 8:38 ` David Jander
2012-09-11 8:48 ` Sascha Hauer
2012-09-11 9:31 ` David Jander
2012-09-11 10:29 ` Michael Olbrich
2012-09-11 10:33 ` Matthew Leach
2012-09-11 10:42 ` David Jander
2012-09-11 13:07 ` Michael Olbrich
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=w51bohddcqw.fsf@mail.mattleach.net \
--to=matthew@mattleach.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.