public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Eric Botcazou <ebotcazou@adacore.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [patch 2/6] scalar-storage-order merge: C front-end
Date: Fri, 19 Jun 2015 09:36:00 -0000	[thread overview]
Message-ID: <1832476.WZxmJhcZbD@polaris> (raw)
In-Reply-To: <alpine.DEB.2.10.1506162110350.31875@digraph.polyomino.org.uk>

> You appear to be duplicating the documentation of an unrelated attribute.

Merge glitch, now fixed, thanks.

> What happens when typeof is applied to a field with reversed storage
> order?

You mean a scalar field contained in an aggregate type with reverse SSO?  Then 
nothing, nothing is changed for scalars on an individual basis, only their 
presence inside an aggregate type with reverse SSO changes something.

> I don't think this type construction is safe when the array type has
> qualified element type.  The following invariant is meant to hold: for an
> array type whose element type (possibly after going down through several
> levels of array types) is qualified, the TYPE_MAIN_VARIANT is a
> corresponding array type whose element type is unqualified.  So in that
> case you need to build two sequences of array types, not one: the main
> variants with unqualified element type, and the versions with qualified
> element type.  See c_build_qualified_type.

I see, will adjust, thanks for the tip.

-- 
Eric Botcazou

  reply	other threads:[~2015-06-19  9:27 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
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 [this message]
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=1832476.WZxmJhcZbD@polaris \
    --to=ebotcazou@adacore.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).