All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: "Richard Röjfors" <richard.rojfors@gmail.com>
Cc: meta-ti@yoctoproject.org
Subject: Re: pandaboard/omap4 support
Date: Wed, 12 Feb 2014 11:28:42 -0500	[thread overview]
Message-ID: <20140212162842.GF4346@edge> (raw)
In-Reply-To: <CAHB-Pj=_sDdkbd0qjZVAWVs0f7c1HMiwfMnm13Ckys-UocVL=A@mail.gmail.com>

On Wed, Feb 12, 2014 at 03:15:38PM +0100, Richard Röjfors wrote:
> On Wed, Feb 12, 2014 at 3:07 PM, Khem Raj <raj.khem@gmail.com> wrote:
> 
> >
> > On Feb 12, 2014, at 6:03 AM, Richard Röjfors <richard.rojfors@gmail.com>
> > wrote:
> >
> > On Wed, Feb 12, 2014 at 2:52 PM, Khem Raj <raj.khem@gmail.com> wrote:
> >
> >>
> >> what incompatibilities do you see between 4.7 and 4.8 ?
> >>
> >
> > I saw this in the gcc 4.8 changelog:
> > "On ARM, a bug has been fixed in GCC's implementation of the AAPCS rules
> > for the layout of vectors that could lead to wrong code being generated.
> > Vectors larger than 8 bytes in size are now by default aligned to an 8-byte
> > boundary. This is an ABI change: code that makes explicit use of vector
> > types may be incompatible with binary objects built with older versions of
> > GCC. Auto-vectorized code is not affected by this change.”
> >
> >
> > OK. are you seeing this use case here ?
> >
> 
> Nope I've not hit it nor gone through the calls between the blobs and the
> surrounding code.
> 
> I just think it makes sense to compile the blobs with a compiler similar to
> the one provided by oe-core, to avoid the risk...

The biggest problem is not 4.7 vs. 4.8, but rather incompatibilities in ABIs 
and call conventions. E.g. we have switched to hardfp for our products and 
some of our components distributed in binary form are only available in hardfp 
format. And oe-core doesn't use hardfp by default yet...

-- 
Denys


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

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-19  5:02 pandaboard/omap4 support Jithin Raj
2013-11-19  6:06 ` Denys Dmytriyenko
2013-11-19  9:32   ` Richard Röjfors
2014-02-12 10:46   ` Richard Röjfors
2014-02-12 13:52     ` Khem Raj
2014-02-12 14:03       ` Richard Röjfors
2014-02-12 14:07         ` Khem Raj
2014-02-12 14:15           ` Richard Röjfors
2014-02-12 16:28             ` Denys Dmytriyenko [this message]
2014-02-12 16:38               ` Khem Raj
2014-02-12 16:41                 ` Denys Dmytriyenko

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=20140212162842.GF4346@edge \
    --to=denys@ti.com \
    --cc=meta-ti@yoctoproject.org \
    --cc=richard.rojfors@gmail.com \
    /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.