Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/1] RFC - Enable GCC 5.3 transactional support
Date: Mon, 29 Feb 2016 22:18:40 -0600	[thread overview]
Message-ID: <cover.1456805735.git.mark.hatle@windriver.com> (raw)

GCC has supported -fgnu-tm, libitm and __transaction_stomic [and related] since
GCC 4.7.  OE however has not activated the functionality.  I'm starting to see some
data base programs (and RPM) that can make use of the functionality to create better
thread-safe code.

This includes a patch to GCC.  I've verified it is working based on the recent rpm
5.4.16 work.  It also should not expand the size of the target unless the user adds
the libitm support to their system.

I'd recommend we consider this patch to enable the additional support.

The following changes since commit 8b7ff912ccaadfc0f355642f2a9f99c334a61253:

  db: remove the NO_UPDATE_REASON and replace it a comment about RPM (2016-02-29 22:13:42 -0600)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib mhatle/gcc-libitm
  http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=mhatle/gcc-libitm

Mark Hatle (1):
  gcc: Add support for atomic opertions (libitm) where available

 meta/recipes-devtools/gcc/gcc-5.3.inc     |  2 ++
 meta/recipes-devtools/gcc/gcc-runtime.inc | 22 +++++++++++++++++++++-
 2 files changed, 23 insertions(+), 1 deletion(-)

-- 
2.5.0



             reply	other threads:[~2016-03-01  4:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-01  4:18 Mark Hatle [this message]
2016-03-01  4:18 ` [PATCH 1/1] gcc: Add support for atomic opertions (libitm) where available Mark Hatle
2016-03-01  6:04   ` Khem Raj

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=cover.1456805735.git.mark.hatle@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=openembedded-core@lists.openembedded.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