public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92010] [8/9/10 Regression] gcc internal error since 8x on warning write-strings
Date: Wed, 08 Apr 2020 14:17:19 +0000	[thread overview]
Message-ID: <bug-92010-4-hT6oyVpn6R@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-92010-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92010

--- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Patrick Palka <ppalka@gcc.gnu.org>:

https://gcc.gnu.org/g:12f55e030ed068d5c7b14c65a74d102db925dab2

commit r10-7622-g12f55e030ed068d5c7b14c65a74d102db925dab2
Author: Patrick Palka <ppalka@redhat.com>
Date:   Mon Mar 30 19:55:03 2020 -0400

    c++: Function type and parameter type disagreements [PR92010]

    This resolves parts of Core issues 1001/1322 by rebuilding the function
type
    of an instantiated function template in terms of its formal parameter types
    whenever the original function type and formal parameter types disagree
about
    the type of a parameter after substitution.

    gcc/cp/ChangeLog:

            Core issues 1001 and 1322
            PR c++/92010
            * pt.c (rebuild_function_or_method_type): Split function out from
...
            (tsubst_function_type): ... here.
            (maybe_rebuild_function_decl_type): New function.
            (tsubst_function_decl): Use it.

    gcc/testsuite/ChangeLog:

            Core issues 1001 and 1322
            PR c++/92010
            * g++.dg/cpp2a/lambda-uneval11.c: New test.
            * g++.dg/template/array33.C: New test.
            * g++.dg/template/array34.C: New test.
            * g++.dg/template/defarg22.C: New test.

  parent reply	other threads:[~2020-04-08 14:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-92010-4@http.gcc.gnu.org/bugzilla/>
2020-03-12 15:29 ` ppalka at gcc dot gnu.org
2020-03-12 22:54 ` ppalka at gcc dot gnu.org
2020-03-12 23:02 ` ppalka at gcc dot gnu.org
2020-03-17 18:34 ` ppalka at gcc dot gnu.org
2020-04-08 14:17 ` cvs-commit at gcc dot gnu.org [this message]
2020-04-08 14:33 ` [Bug c++/92010] [8/9 " ppalka at gcc dot gnu.org
2021-04-21 21:25 ` ppalka at gcc dot gnu.org
2021-10-05  9:55 ` nickhuang99 at hotmail dot com
2021-10-05 14:23 ` ppalka at gcc dot gnu.org
2021-10-05 16:21 ` nickhuang99 at hotmail dot com
2021-10-05 21:05 ` ppalka at gcc dot gnu.org
2021-10-05 21:56 ` nickhuang99 at hotmail dot com
2021-10-05 22:08 ` nickhuang99 at hotmail dot com

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-92010-4-hT6oyVpn6R@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).