public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joe Buck <Joe.Buck@synopsys.COM>
To: Sebastian Pop <sebpop@gmail.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: C/C++ extensions for array notations
Date: Mon, 13 Dec 2010 17:47:00 -0000	[thread overview]
Message-ID: <20101213174734.GC19689@synopsys.com> (raw)
In-Reply-To: <AANLkTinmQeuo6NeEZg9RMq38SxgAXijF4R7=0D1bEEQU@mail.gmail.com>

On Mon, Dec 13, 2010 at 09:08:39AM -0800, Sebastian Pop wrote:
> Hi,
> 
> I would like to ask the opinion of C/C++ maintainers about the extension
> that the Intel compiler proposes for array notations:
> http://software.intel.com/sites/products/documentation/studio/composer/en-us/2011/compiler_c/index.htm#optaps/common/optaps_par_cean_prog.htm
> 
> Are there strong opinions against this extension?

It's an interesting concept, looks especially useful for parallel
programming.  It looks like a very complex set of features; I don't
know whether Intel has a document elsewhere that specifies the details.
Because of the high complexity, it could be quite a maintainance burden,
especially if there isn't a rigorous spec.

Interaction with other C++ language features doesn't seem to be described.
I can't think of a standard C++ program that would change meaning with
this extension.  But it's not stated whether there can be a reference to
an array section, what the ABI looks like when an array section is
passed as a C++ function argument, whether there are any issues when the
base type of the array we're taking a section of has constructors and
destructors, etc.

If someone is interested in producing an experimental gcc extension,
great.  But there would be a lot of questions to be answered before
it would be appropriate to accept as a supported feature of GCC.





  parent reply	other threads:[~2010-12-13 17:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-13 17:09 Sebastian Pop
2010-12-13 17:43 ` Joseph S. Myers
2010-12-13 17:47 ` Joe Buck [this message]
2010-12-15  2:10 ` Richard Guenther

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=20101213174734.GC19689@synopsys.com \
    --to=joe.buck@synopsys.com \
    --cc=gcc@gcc.gnu.org \
    --cc=sebpop@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).