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++/112588] [modules] ICE in make_decl_rtl when returning str literal when string header imported in module
Date: Wed, 17 Jan 2024 23:48:51 +0000	[thread overview]
Message-ID: <bug-112588-4-eW35JytKnl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112588-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Nathaniel Shead <nshead@gcc.gnu.org>:

https://gcc.gnu.org/g:3471a61ed0ddef70de8f1bbba85cd1e945fc86fd

commit r14-8196-g3471a61ed0ddef70de8f1bbba85cd1e945fc86fd
Author: Nathaniel Shead <nathanieloshead@gmail.com>
Date:   Sat Dec 16 21:34:45 2023 +1100

    c++: Prevent overwriting arguments when merging duplicates [PR112588]

    When merging duplicate instantiations of function templates, currently
    read_function_def overwrites the arguments with that of the existing
    duplicate. This is problematic, however, since this means that the
    PARM_DECLs in the body of the function definition no longer match with
    the PARM_DECLs in the argument list, which causes issues when it comes
    to generating RTL.

    There doesn't seem to be any reason to do this replacement, so this
    patch removes that logic.

            PR c++/112588

    gcc/cp/ChangeLog:

            * module.cc (trees_in::read_function_def): Don't overwrite
            arguments.

    gcc/testsuite/ChangeLog:

            * g++.dg/modules/merge-16.h: New test.
            * g++.dg/modules/merge-16_a.C: New test.
            * g++.dg/modules/merge-16_b.C: New test.

    Signed-off-by: Nathaniel Shead <nathanieloshead@gmail.com>

  parent reply	other threads:[~2024-01-17 23:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-17 14:24 [Bug c++/112588] New: " nickbegg at gmail dot com
2023-11-18  0:40 ` [Bug c++/112588] " nathanieloshead at gmail dot com
2023-12-01  9:10 ` pinskia at gcc dot gnu.org
2024-01-08 17:06 ` ppalka at gcc dot gnu.org
2024-01-17 23:48 ` cvs-commit at gcc dot gnu.org [this message]
2024-01-19  1:00 ` [Bug c++/112588] [modules] " hp at gcc dot gnu.org
2024-01-27 10:31 ` nshead at gcc dot gnu.org
2024-03-06 22:08 ` ppalka 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-112588-4-eW35JytKnl@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).