From: Hans-Peter Nilsson <hp@bitrange.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org, amacleod@redhat.com
Subject: Re: Implement C11 _Atomic
Date: Thu, 21 Nov 2013 13:19:00 -0000 [thread overview]
Message-ID: <alpine.BSF.2.02.1311210545480.43309@arjuna.pair.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1311052316480.30260@digraph.polyomino.org.uk>
On Tue, 5 Nov 2013, Joseph S. Myers wrote:
Thanks for doing this! However, without examples I have trouble
reading out the bits I need as a target maintainer, and I can't
read out the answers from the patch, so pardon a few questions.
> This patch, relative to trunk and based on work done on the C11-atomic
> branch, adds support for C11 _Atomic. It is intended to include all
> the required language support.
>
> It does not include the <stdatomic.h> header; there's a version on the
> branch, but it needs further review against the standard and test
> coverage adding to the testsuite before I can propose it for mainline.
>
> Support for atomic types having bigger alignment than the
> corresponding non-atomic types is limited: it includes the code to
> increase the alignment of types whose size is exactly 1, 2, 4, 8 or 16
> to that of the corresponding integer type [*], but not anything for
> target-specific alignment increases.
Target-maintainer perspective here: do I read that correctly,
that by default adding _Atomic raises the alignment of that type
to the "natural" one, for all targets?
To wit,
> There's code for target-specific
> alignment on the branch (and I intend to merge trunk back to the
> branch once this patch is on trunk, so it's easy to tell what the
> changes still left on the branch are), should any target maintainers
> wish to have such alignment.
...is that part needed for alignment that is only
target-specific and other-than-natural? For example, 8-byte
aligment where required for atomic 4-byte types?
Or is that part also required for
anything-other-than-ordinary-C-type alignment for the target;
say, natural 4-byte alignment of 4-byte-types for targets where
alignment is otherwise "packed"; where only 1-byte alignment of
the basic type is ABI-mandated?
brgds, H-P
next prev parent reply other threads:[~2013-11-21 11:05 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
2013-11-21 13:19 ` Hans-Peter Nilsson [this message]
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=alpine.BSF.2.02.1311210545480.43309@arjuna.pair.com \
--to=hp@bitrange.com \
--cc=amacleod@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.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).