public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] arm: Switch to -mno-unaligned-access when supported by the compiler
Date: Wed, 12 Feb 2014 17:19:15 +0100	[thread overview]
Message-ID: <20140212171915.57e9c715@lilith> (raw)
In-Reply-To: <20140212143555.GB15819@bill-the-cat>

Hi Tom,

On Wed, 12 Feb 2014 09:35:55 -0500, Tom Rini <trini@ti.com> wrote:

> On Tue, Feb 11, 2014 at 05:37:55PM +0100, Albert ARIBAUD wrote:
> > Hi M?ns,
> > 
> > On Tue, 11 Feb 2014 15:33:09 +0000, M?ns Rullg?rd <mans@mansr.com>
> > wrote:
> > 
> > > The problem is that the current settings do
> > > the exact opposite.  By using -munaligned-access by default, you are
> > > asking the compiler to go ahead and do whatever it thinks is best, which
> > > is sometimes to perform an intentional unaligned access.  Exactly when
> > > this will happen is largely impossible to predict.
> > 
> > The -munaligned-access option does *not* "[ask] the compiler to go
> > ahead and do whatever it thinks is best", it tells it to use direct
> > native accesses when unaligned accesses are required, as opposed to
> > splitting unaligned accesses into smaller but aligned aligned native
> > accesses, which is what you get with -mno-unaligned-access.
> 
> Incorrect, and gets to the heart of our problem.  It says that native
> unaligned accesses are valid and make use of this as appropriate.  So
> our goal of "make the compiler use native unaligned accesses so we can
> find bad code" is invalid.  It's making properly written code fail
> instead and improperly written code will still be just as improper.

Code which translates into uncontrolled unaligned accesses is not
properly written.

Amicalement,
-- 
Albert.

  reply	other threads:[~2014-02-12 16:19 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-04 17:05 [U-Boot] [PATCH v2] arm: Switch to -mno-unaligned-access when supported by the compiler Tom Rini
2014-02-04 17:35 ` Måns Rullgård
2014-02-10  9:24 ` Albert ARIBAUD
2014-02-10 13:21   ` Tom Rini
2014-02-10 14:57     ` Albert ARIBAUD
2014-02-10 15:14       ` Måns Rullgård
2014-02-10 15:40         ` Måns Rullgård
2014-02-10 16:12         ` Albert ARIBAUD
2014-02-10 16:21           ` Måns Rullgård
2014-02-10 16:24           ` Tom Rini
2014-02-10 17:26             ` Albert ARIBAUD
2014-02-10 18:54               ` Wolfgang Denk
2014-02-10 21:26               ` Tom Rini
2014-02-10 22:17                 ` Wolfgang Denk
2014-02-10 22:28                   ` Tom Rini
2014-02-11  8:19                     ` Wolfgang Denk
2014-02-11 12:37                       ` Måns Rullgård
2014-02-11 14:43                         ` Wolfgang Denk
2014-02-11 15:33                           ` Måns Rullgård
2014-02-11 16:37                             ` Albert ARIBAUD
2014-02-11 16:44                               ` Måns Rullgård
2014-02-11 17:11                                 ` Albert ARIBAUD
2014-02-11 17:21                                   ` Albert ARIBAUD
2014-02-12 14:35                               ` Tom Rini
2014-02-12 16:19                                 ` Albert ARIBAUD [this message]
2014-02-17 15:45                                   ` Tom Rini
2014-02-17 15:55                                     ` Albert ARIBAUD
2014-02-11 18:18                             ` Wolfgang Denk
2014-02-11 18:21                               ` Måns Rullgård
2014-02-11  8:44                     ` Albert ARIBAUD
2014-02-12 14:25                       ` Tom Rini
2014-02-12 15:51                         ` Wolfgang Denk
2014-02-10 15:21       ` Tom Rini

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=20140212171915.57e9c715@lilith \
    --to=albert.u.boot@aribaud.net \
    --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