Openembedded Core Discussions
 help / color / mirror / Atom feed
* [PATCH 0/1] RFC - Enable GCC 5.3 transactional support
@ 2016-03-01  4:18 Mark Hatle
  2016-03-01  4:18 ` [PATCH 1/1] gcc: Add support for atomic opertions (libitm) where available Mark Hatle
  0 siblings, 1 reply; 3+ messages in thread
From: Mark Hatle @ 2016-03-01  4:18 UTC (permalink / raw)
  To: openembedded-core

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



^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2016-03-01  6:04 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-03-01  4:18 [PATCH 0/1] RFC - Enable GCC 5.3 transactional support Mark Hatle
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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox