From: Andrew Pinski <pinskia@gmail.com>
To: Ramana Radhakrishnan <ramana.radhakrishnan@foss.arm.com>
Cc: Eric Botcazou <ebotcazou@adacore.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch 2/6] scalar-storage-order merge: C front-end
Date: Tue, 16 Jun 2015 09:11:00 -0000 [thread overview]
Message-ID: <CA+=Sn1kd1Ww44cKeBnbKfPbULVzpRC1S+GWTehQeDLj6HWt7HA@mail.gmail.com> (raw)
In-Reply-To: <557FE6FA.9020803@foss.arm.com>
On Tue, Jun 16, 2015 at 2:06 AM, Ramana Radhakrishnan
<ramana.radhakrishnan@foss.arm.com> wrote:
>
>
> On 16/06/15 09:54, Eric Botcazou wrote:
>>
>> This is the C front-end + C family part.
>>
>> * doc/extend.texi (type attributes): Document
>> scalar_storage_order.
>> * doc/invoke.texi (Warnings): Document -Wno-scalar-storage-order.
>> c-family/
>> * c-common.c (c_common_attributes): Add scalar_storage_order.
>> (handle_scalar_storage_order_attribute): New function.
>> * c.opt (Wscalar-storage-order): New warning.
>> c/
>> * c-decl.c (finish_struct): If the structure has reverse scalar
>> storage
>> order, rewrite the type of array fields with scalar component.
>> * c-typeck.c (build_unary_op) <ADDR_EXPR>: Remove left-overs.
>> Issue
>> errors on bit-fields and reverse SSO here and not...
>> (c_mark_addressable): ...here.
>>
>> doc/extend.texi | 47 +++++++++++++++++++++++++++++++++++++++++++++
>> doc/invoke.texi | 6 +++++
>> c-family/c.opt | 4 +++
>> c-family/c-common.c | 54
>> +++++++++++++++++++++++++++++++++++++++++++++++++-
>> c/c-typeck.c | 53
>> +++++++++++++++++++++++++++++++-------------------
>> c/c-decl.c | 45 +++++++++++++++++++++++++++++--------------
>> 6 files changed, 175 insertions(+), 34 deletions(-)
>>
>
> A very cursory glance at the patch set but should we restrict this attribute
> to apply only to scalar types rather than allow them on vector extensions.
> I haven't had enough coffee this morning but a first thought is that if it
> does apply on vector type extensions, clarifying the lane ordering up front
> would be helpful especially as we now allow indexing into short vectors.
I think it applies to vector types but really it acts the same way as
we apply attributes on arrays, that is on the inner scalar type
instead.
Thanks,
Andrew
>
>
> regards
> Ramana
>
>
>
next prev parent reply other threads:[~2015-06-16 9:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 8:46 [patch 0/6] scalar-storage-order merge Eric Botcazou
2015-06-16 8:52 ` [patch 1/6] scalar-storage-order merge: Ada front-end Eric Botcazou
2015-06-16 8:56 ` [patch 2/6] scalar-storage-order merge: C front-end Eric Botcazou
2015-06-16 9:07 ` Ramana Radhakrishnan
2015-06-16 9:11 ` Andrew Pinski [this message]
2015-06-18 19:16 ` Eric Botcazou
2015-06-16 11:39 ` Richard Sandiford
2015-06-18 19:17 ` Eric Botcazou
2015-06-16 21:25 ` Joseph Myers
2015-06-19 9:36 ` Eric Botcazou
2015-06-16 8:59 ` [patch 3/6] scalar-storage-order merge: C++ front-end Eric Botcazou
2015-06-16 9:24 ` [patch 4/6] scalar-storage-order merge: bulk Eric Botcazou
2015-06-16 9:53 ` [patch 5/6] scalar-storage-order merge: rest Eric Botcazou
2015-06-16 9:59 ` [patch 6/6] scalar-storage-order merge: testsuite Eric Botcazou
2015-06-16 13:30 ` Richard Earnshaw
2015-06-18 20:29 ` Eric Botcazou
2015-06-19 9:17 ` Eric Botcazou
2015-10-06 10:57 [patch 0/6] scalar-storage-order merge (2) Eric Botcazou
2015-10-06 11:02 ` [patch 2/6] scalar-storage-order merge: C front-end Eric Botcazou
2015-10-13 11:32 ` Jeff Law
2015-10-19 8:50 ` Eric Botcazou
2015-10-28 16:48 ` Joseph Myers
2015-10-28 17:32 ` Jeff Law
2015-10-28 22:34 ` Eric Botcazou
2015-10-28 23:36 ` Mike Stump
2015-10-29 0:23 ` Joseph Myers
2015-10-30 8:59 ` Eric Botcazou
2015-10-30 14:50 ` Mike Stump
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='CA+=Sn1kd1Ww44cKeBnbKfPbULVzpRC1S+GWTehQeDLj6HWt7HA@mail.gmail.com' \
--to=pinskia@gmail.com \
--cc=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ramana.radhakrishnan@foss.arm.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).