public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/53094] constexpr vector subscripting
Date: Tue, 11 Dec 2012 20:20:00 -0000	[thread overview]
Message-ID: <bug-53094-4-qR6O3nHNqR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53094-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53094

--- Comment #14 from Marc Glisse <glisse at gcc dot gnu.org> 2012-12-11 20:20:34 UTC ---
Author: glisse
Date: Tue Dec 11 20:20:23 2012
New Revision: 194421

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=194421
Log:
2012-12-11  Marc Glisse  <marc.glisse@inria.fr>

    PR c++/53094
cp/
    * tree.c (cp_tree_equal): Handle VECTOR_CST.
    * semantics.c (cxx_eval_bare_aggregate): Protect a dereference.
    Handle VECTOR_CST.
testsuite/
    * g++.dg/cpp0x/constexpr-53094-1.C: New testcase.
    * g++.dg/cpp0x/constexpr-53094-2.C: Likewise.
    * g++.dg/cpp0x/constexpr-53094-3.C: Likewise.


Added:
    trunk/gcc/testsuite/g++.dg/cpp0x/constexpr-53094-1.C   (with props)
    trunk/gcc/testsuite/g++.dg/cpp0x/constexpr-53094-2.C   (with props)
    trunk/gcc/testsuite/g++.dg/cpp0x/constexpr-53094-3.C   (with props)
Modified:
    trunk/gcc/cp/ChangeLog
    trunk/gcc/cp/semantics.c
    trunk/gcc/cp/tree.c
    trunk/gcc/testsuite/ChangeLog

Propchange: trunk/gcc/testsuite/g++.dg/cpp0x/constexpr-53094-1.C
            ('svn:eol-style' added)

Propchange: trunk/gcc/testsuite/g++.dg/cpp0x/constexpr-53094-1.C
            ('svn:keywords' added)

Propchange: trunk/gcc/testsuite/g++.dg/cpp0x/constexpr-53094-2.C
            ('svn:eol-style' added)

Propchange: trunk/gcc/testsuite/g++.dg/cpp0x/constexpr-53094-2.C
            ('svn:keywords' added)

Propchange: trunk/gcc/testsuite/g++.dg/cpp0x/constexpr-53094-3.C
            ('svn:eol-style' added)

Propchange: trunk/gcc/testsuite/g++.dg/cpp0x/constexpr-53094-3.C
            ('svn:keywords' added)


  parent reply	other threads:[~2012-12-11 20:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-23 20:14 [Bug c++/53094] New: vector literal marc.glisse at normalesup dot org
2012-11-26 23:18 ` [Bug c++/53094] " glisse at gcc dot gnu.org
2012-11-28 17:26 ` glisse at gcc dot gnu.org
2012-11-28 21:11 ` glisse at gcc dot gnu.org
2012-11-28 21:53 ` glisse at gcc dot gnu.org
2012-11-29 15:40 ` glisse at gcc dot gnu.org
2012-11-29 15:45 ` [Bug c++/53094] constexpr vector subscripting glisse at gcc dot gnu.org
2012-12-03 14:30 ` vincenzo.innocente at cern dot ch
2012-12-03 14:54 ` glisse at gcc dot gnu.org
2012-12-03 19:15 ` vincenzo.innocente at cern dot ch
2012-12-03 19:53 ` glisse at gcc dot gnu.org
2012-12-03 21:58 ` vincenzo.innocente at cern dot ch
2012-12-03 22:05 ` vincenzo.innocente at cern dot ch
2012-12-03 22:31 ` glisse at gcc dot gnu.org
2012-12-11 20:20 ` glisse at gcc dot gnu.org [this message]
2013-07-09 16:02 ` glisse at gcc dot gnu.org
2013-07-09 16:10 ` glisse at gcc dot gnu.org

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=bug-53094-4-qR6O3nHNqR@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).