public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jason Merrill <jason@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: gcc-patches List <gcc-patches@gcc.gnu.org>
Subject: Re: [C++ PATCH] Handle CASE_HIGH in constexpr evaluation (PR c++/72868)
Date: Thu, 11 Aug 2016 15:46:00 -0000	[thread overview]
Message-ID: <CADzB+2=TsXd-1=re79K93_kP74SE3SPUQ7b2qGQarSENJdxpDg@mail.gmail.com> (raw)
In-Reply-To: <20160811145516.GS14857@tucnak.redhat.com>

OK for trunk and 6.

On Thu, Aug 11, 2016 at 10:55 AM, Jakub Jelinek <jakub@redhat.com> wrote:
> Hi!
>
> As mentioned in the PR, constexpr.c has been handling cases with ranges
> just as the lowest value of the range.
>
> Fixed thusly, bootstrapped/regtested on x86_64-linux and i686-linux, ok for
> trunk?  What about 6.2 (not a regression, but low risk fix for wrong-code)?
>
> 2016-08-11  Jakub Jelinek  <jakub@redhat.com>
>
>         PR c++/72868
>         * constexpr.c (label_matches): Handle case range expressions.
>
>         * g++.dg/cpp1y/constexpr-switch4.C: New test.
>
> --- gcc/cp/constexpr.c.jj       2016-08-10 00:21:07.000000000 +0200
> +++ gcc/cp/constexpr.c  2016-08-10 22:17:16.577041975 +0200
> @@ -3448,6 +3448,12 @@ label_matches (tree *jump_target, tree_s
>         {
>           if (!CASE_LOW (stmt))
>             default_label = i;
> +         else if (CASE_HIGH (stmt))
> +           {
> +             if (tree_int_cst_le (CASE_LOW (stmt), *jump_target)
> +                 && tree_int_cst_le (*jump_target, CASE_HIGH (stmt)))
> +               return true;
> +           }
>           else if (tree_int_cst_equal (*jump_target, CASE_LOW (stmt)))
>             return true;
>         }
> --- gcc/testsuite/g++.dg/cpp1y/constexpr-switch4.C.jj   2016-08-10 22:22:29.567129868 +0200
> +++ gcc/testsuite/g++.dg/cpp1y/constexpr-switch4.C      2016-08-10 22:23:25.104435699 +0200
> @@ -0,0 +1,27 @@
> +// PR c++/72868
> +// { dg-do compile }
> +// { dg-options "-std=gnu++14" }
> +
> +constexpr int
> +foo (int i)
> +{
> +  switch (i)
> +    {
> +    case 11 ... 12:
> +      return 4;
> +    case 0 ... 9:
> +      return 3;
> +    default:
> +      return 7;
> +    }
> +}
> +
> +#define SA(X) static_assert((X),#X)
> +SA (foo (-1) == 7);
> +SA (foo (0) == 3);
> +SA (foo (3) == 3);
> +SA (foo (9) == 3);
> +SA (foo (10) == 7);
> +SA (foo (11) == 4);
> +SA (foo (12) == 4);
> +SA (foo (13) == 7);
>
>         Jakub

      reply	other threads:[~2016-08-11 15:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-11 14:55 Jakub Jelinek
2016-08-11 15:46 ` Jason Merrill [this message]

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='CADzB+2=TsXd-1=re79K93_kP74SE3SPUQ7b2qGQarSENJdxpDg@mail.gmail.com' \
    --to=jason@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.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).