From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-patches-return-468170-listarch-gcc-patches=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 125156 invoked by alias); 29 Nov 2017 21:03:33 -0000
Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-patches.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-patches/>
List-Post: <mailto:gcc-patches@gcc.gnu.org>
List-Help: <mailto:gcc-patches-help@gcc.gnu.org>
Sender: gcc-patches-owner@gcc.gnu.org
Received: (qmail 125142 invoked by uid 89); 29 Nov 2017 21:03:32 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-3.1 required=5.0 tests=AWL,BAYES_00,KB_WAM_FROM_NAME_SINGLEWORD,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 spammy=HTo:D*fr
X-HELO: mail-it0-f53.google.com
Received: from mail-it0-f53.google.com (HELO mail-it0-f53.google.com) (209.85.214.53) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 29 Nov 2017 21:03:31 +0000
Received: by mail-it0-f53.google.com with SMTP id t1so5687988ite.5        for <gcc-patches@gcc.gnu.org>; Wed, 29 Nov 2017 13:03:31 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=1e100.net; s=20161025;        h=x-gm-message-state:mime-version:in-reply-to:references:from:date         :message-id:subject:to:cc;        bh=XREqEyB69LmXQyBq4kQcGYDYJxsRKfleHfrrAtZPOT0=;        b=dTIpmOHbtNJK/u8Tj057HCXRqRku0BfORL4dWwi/9KupVYRLTsmTsht/yzm2IxHeKV         7J4LQqBosX0yRSncfE4aSwdLssrjkUoIXLUN6QH/bGbMk6vDu7jX7PT1J7hi8Lc53tvA         s1Qap3Lxa9wWJzBvZXTWPWGEQ1MmeZ1WkZBXTNH5m4cA7F4wNoKrVItXdPenpXcdw3n9         HcNMjw8lN6E0SWQ2vVXK3XqZb/8o6W4/lOz40FrD1bKqlNRaO6LTucFzGvGTMvdDNMFP         RViWu6nGwZrU8gmXmUSu935iqUqwHv/yPrJssM/7q8HhmdMWV2f6aL6Bt7+1vuCenPbQ         wE6w==
X-Gm-Message-State: AJaThX5xIO5NGEGZhwD6kNJeDf+UuQEUxl9/uXYqus25IyGY1xIyqnH/	SthQu8Qn7yW1rq3o+JRsnEV28brrwKmQfuWg3N8TGg==
X-Google-Smtp-Source: AGs4zMbRuzXnF3bKDuQ0PT3Em0qagL3uh7wO/fVoMjFzgAwZrgR02hg8yCDO/HGA4SWhBlZGslc6Oe0BKId8tUd8y58=
X-Received: by 10.36.80.148 with SMTP id m142mr248824itb.6.1511989409948; Wed, 29 Nov 2017 13:03:29 -0800 (PST)
MIME-Version: 1.0
Received: by 10.107.171.134 with HTTP; Wed, 29 Nov 2017 13:03:09 -0800 (PST)
In-Reply-To: <alpine.DEB.2.21.1711241424080.6330@stedding.saclay.inria.fr>
References: <CADzB+2kJRV14hZX1rGz5V_UCpSB7MdVQPh4OM=vYOsw6ZDUNkA@mail.gmail.com> <alpine.DEB.2.21.1711241424080.6330@stedding.saclay.inria.fr>
From: Jason Merrill <jason@redhat.com>
Date: Wed, 29 Nov 2017 21:23:00 -0000
Message-ID: <CADzB+2nt6zNz+ucM_GF6fe0oJVScQ2p3AyXO7hd94pAJ_ReQRA@mail.gmail.com>
Subject: Re: RFA (libstdc++): PATCH to implement C++17 over-aligned new
To: Marc Glisse <marc.glisse@inria.fr>
Cc: gcc-patches List <gcc-patches@gcc.gnu.org>
Content-Type: text/plain; charset="UTF-8"
X-IsSubscribed: yes
X-SW-Source: 2017-11/txt/msg02513.txt.bz2

On Fri, Nov 24, 2017 at 8:31 AM, Marc Glisse <marc.glisse@inria.fr> wrote:
> Hello,
>
> @@ -4247,9 +4248,20 @@ build_operator_new_call (tree fnname, vec<tree,
> va_gc> **args,
>       we disregard block-scope declarations of "operator new".  */
>    fns = lookup_function_nonclass (fnname, *args, /*block_p=*/false);
>
> +  if (align_arg)
> +    {
> +      vec<tree, va_gc>* align_args
> +       = vec_copy_and_insert (*args, align_arg, 1);
> +      cand = perform_overload_resolution (fns, align_args, &candidates,
> +                                         &any_viable_p, tf_none);
> +      /* If no aligned allocation function matches, try again without the
> +        alignment.  */
> +    }
> +
>
> Code further in the function expects to be able to adjust args, which is
> defeated by copying them in align_args, see PR 82760.

Fixed, thanks.