public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/56620] Memcpy optimization may lead to unaligned access on ARM Thumb Date: Thu, 14 Mar 2013 20:33:00 -0000 [thread overview] Message-ID: <bug-56620-4-222jSnJFVe@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56620-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56620 --- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> 2013-03-14 20:33:27 UTC --- I think you are required to use -mno-unaligned-access for armv7 targets where you doing bare metal work without the page table setup.
next prev parent reply other threads:[~2013-03-14 20:33 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-03-14 18:12 [Bug c/56620] New: " eleventen at gmail dot com 2013-03-14 18:13 ` [Bug c/56620] " eleventen at gmail dot com 2013-03-14 18:20 ` [Bug target/56620] " pinskia at gcc dot gnu.org 2013-03-14 18:26 ` eleventen at gmail dot com 2013-03-14 20:33 ` pinskia at gcc dot gnu.org [this message] 2013-03-14 21:06 ` eleventen at gmail dot com 2013-03-14 21:36 ` eleventen at gmail dot com
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=bug-56620-4-222jSnJFVe@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).