From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] [RFC] arm: fix memset-related crashes caused by recent GCC (4.7.2) optimizations
Date: Mon, 11 Feb 2013 18:41:14 +0000 [thread overview]
Message-ID: <20130211184114.GP9801@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <1359793988-6881-1-git-send-email-ivan.djelic@parrot.com>
On Sat, Feb 02, 2013 at 08:33:08AM +0000, Ivan Djelic wrote:
> Recent GCC versions (e.g. GCC-4.7.2) perform optimizations based on
> assumptions about the implementation of memset and similar functions.
> The current ARM optimized memset code does not return the value of
> its first argument, as is usually expected from standard implementations.
How does GCC do this? By strcmping the function name and assuming that
memset is a libc implementation?
If so, maybe passing something like -ffreestanding would make sense to turn
this behaviour off in the compiler (otherwise we should also vet the rest of
the standard string functions).
Will
next prev parent reply other threads:[~2013-02-11 18:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-02 8:33 [PATCH] [RFC] arm: fix memset-related crashes caused by recent GCC (4.7.2) optimizations Ivan Djelic
2013-02-09 11:05 ` Ivan Djelic
2013-02-09 14:48 ` Nicolas Pitre
2013-02-11 12:35 ` Ivan Djelic
2013-02-11 18:17 ` Ben Dooks
2013-02-11 21:39 ` Ivan Djelic
2013-02-11 18:41 ` Will Deacon [this message]
2013-02-11 19:42 ` Ivan Djelic
2013-02-12 14:00 ` Will Deacon
2013-02-12 15:58 ` Russell King - ARM Linux
2013-02-12 16:36 ` Will Deacon
2013-02-12 16:37 ` Russell King - ARM Linux
2013-02-12 16:38 ` Will Deacon
2013-03-05 13:50 ` Dirk Behme
2013-03-06 1:42 ` Will Deacon
2013-03-06 7:05 ` Dirk Behme
2013-03-06 17:11 ` Russell King - ARM Linux
2013-03-06 17:38 ` Dirk Behme
2013-03-06 18:43 ` Russell King - ARM Linux
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=20130211184114.GP9801@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--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;
as well as URLs for NNTP newsgroup(s).