From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Andrew MacLeod <amacleod@redhat.com>,
Mike Stump <mikestump@comcast.net>, <stanshebs@earthlink.net>,
Jason Merrill <jason@redhat.com>,
Richard Henderson <rth@redhat.com>, "jh@suse.cz" <jh@suse.cz>
Subject: Re: Implement C11 _Atomic
Date: Fri, 08 Nov 2013 13:33:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1311081309110.3062@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CAFULd4ZbQ+XOQDvPuXS7j5zsKGvbow6i0rXG4zHVD-KGkV4YHw@mail.gmail.com>
On Fri, 8 Nov 2013, Uros Bizjak wrote:
> Can we introduce a target-dependant source here, in the same way as
Sure, that seems a reasonable thing to do. I think putting a file fenv.c
in an appropriate subdirectory of libatomic/config will result in it being
found automatically by the existing search path logic, but you'll need to
test that.
The present code essentially follows what glibc's feraiseexcept does for
lots of architectures, but with generic C code where the glibc code tends
to use asms to control the exact instructions used (and thereby avoid the
need for volatile, I suppose).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2013-11-08 13:13 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 0:44 Joseph S. Myers
2013-11-06 22:42 ` Andrew MacLeod
2013-11-07 17:16 ` Uros Bizjak
2013-11-07 17:24 ` Jakub Jelinek
2013-11-07 18:10 ` Uros Bizjak
2013-11-07 18:44 ` Joseph S. Myers
2013-11-07 18:47 ` Uros Bizjak
2013-11-07 18:55 ` Joseph S. Myers
[not found] ` <CAFULd4ZrAEECG+pptH8cRaWznioaM9VXS4TetpEvkWj--n7H1w@mail.gmail.com>
2013-11-07 21:02 ` Joseph S. Myers
2013-11-07 21:08 ` Uros Bizjak
2013-11-07 22:25 ` Uros Bizjak
2013-11-07 22:43 ` Joseph S. Myers
2013-11-08 10:09 ` Uros Bizjak
2013-11-08 13:33 ` Joseph S. Myers [this message]
2013-11-21 13:19 ` Hans-Peter Nilsson
2013-11-21 18:03 ` Andrew MacLeod
2013-11-21 18:20 ` Hans-Peter Nilsson
2013-11-21 18:30 ` Andrew MacLeod
2013-11-21 18:49 ` Joseph S. Myers
2013-11-21 18:58 ` Andrew MacLeod
2013-11-21 19:24 ` Hans-Peter Nilsson
2013-11-22 2:57 ` Hans-Peter Nilsson
2013-11-22 3:03 ` Andrew MacLeod
2013-11-22 3:32 ` Hans-Peter Nilsson
2013-11-22 3:32 ` Joseph S. Myers
2013-11-22 19:12 ` Andrew MacLeod
2013-11-22 20:01 ` Hans-Peter Nilsson
2013-11-08 13:28 Dominique Dhumieres
2013-11-08 13:34 ` Joseph S. Myers
2013-11-08 13:43 ` Dominique Dhumieres
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=Pine.LNX.4.64.1311081309110.3062@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=amacleod@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jason@redhat.com \
--cc=jh@suse.cz \
--cc=mikestump@comcast.net \
--cc=rth@redhat.com \
--cc=stanshebs@earthlink.net \
--cc=ubizjak@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 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).