public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andres Tiraboschi <andres.tiraboschi@tallertechnologies.com>
To: Joseph Myers <joseph@codesourcery.com>,
	GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Adding warning for constexpr's
Date: Mon, 15 Jun 2015 19:58:00 -0000	[thread overview]
Message-ID: <CAJZwEL=akue+uiwsjnNFY650DwEVLUa_C_rNpAEWwXPeG4zHXQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1506122133340.17561@digraph.polyomino.org.uk>

2015-06-12 18:35 GMT-03:00 Joseph Myers <joseph@codesourcery.com>:
> On Fri, 12 Jun 2015, Andres Tiraboschi wrote:
>
>> Hi, this patch is for adding a warning when a constexpr cannot be evaluated at compile time.
>> This is a single case:
>> type var = fun(args...), with fun declared as a constexpr.
>
> All options need documenting in invoke.texi.  All diagnostics need
> testcases added to the testsuite.  C++-specific options go in c.opt and
> should be listed as C++ ObjC++, not Common.  All new diagnostics should
> use warning_at etc. with explicit locations passed, unless there is some
> strong reason it's hard to get the relevant location when the warning is
> given.
>
> --
> Joseph S. Myers
> joseph@codesourcery.com

Hi, do you know where is the .exp file for the tests in
.../gcc/testsuite/g++.dg/warn?
I can't find it. Thanks again

  parent reply	other threads:[~2015-06-15 19:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-12 21:35 Andres Tiraboschi
2015-06-13  2:33 ` Joseph Myers
2015-06-15 15:12   ` Andres Tiraboschi
2015-06-15 19:58   ` Andres Tiraboschi [this message]
2015-06-16  0:39     ` 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='CAJZwEL=akue+uiwsjnNFY650DwEVLUa_C_rNpAEWwXPeG4zHXQ@mail.gmail.com' \
    --to=andres.tiraboschi@tallertechnologies.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).