From: JUJU DUDU <acc.gccquestions@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: Gcc transactional memory. Usable?
Date: Tue, 26 Apr 2022 13:20:21 +0200 [thread overview]
Message-ID: <CACS5Re_=wpk2Zjja6+LbsqLeUFt-hyR-J5xZF=uzVrt441JJsg@mail.gmail.com> (raw)
I use gcc 11.2 on Linux.
Would you consider transactional memory usable in production? Is it
performance oriented?
I consider it to replace some code using binary semaphore.
The ultimate goal is to transfer the responsibility from the dev to the
compiler so that mistakes are avoided.
There are so few resources talking about it. Especially if you ran into
bugs or undefined behaviors. The goal here is to leverage your experience
to make my move.
Thanks
reply other threads:[~2022-04-26 11:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CACS5Re_=wpk2Zjja6+LbsqLeUFt-hyR-J5xZF=uzVrt441JJsg@mail.gmail.com' \
--to=acc.gccquestions@gmail.com \
--cc=gcc-help@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: 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).