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++/114572] [OpenMP] "internal compiler error: in assign_temp" with assignment operator and lastprivate clause
Date: Sun, 21 Apr 2024 04:08:55 +0000	[thread overview]
Message-ID: <bug-114572-4-XRlsXCE1lW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114572-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-13 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:910fa4d9df8f72d16279324cca2bf1f2649aa68b

commit r13-8627-g910fa4d9df8f72d16279324cca2bf1f2649aa68b
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Fri Apr 5 09:31:28 2024 +0200

    c++: Fix ICE with weird copy assignment operator [PR114572]

    While ctors/dtors don't return anything (undeclared void or this pointer
    on arm) and copy assignment operators normally return a reference to *this,
    it isn't invalid to return uselessly some class object which might need
    destructing, but the OpenMP clause handling code wasn't expecting that.

    The following patch fixes that.

    2024-04-05  Jakub Jelinek  <jakub@redhat.com>

            PR c++/114572
            * cp-gimplify.cc (cxx_omp_clause_apply_fn): Call build_cplus_new
            on build_call_a result if it has class type.

            * testsuite/libgomp.c++/pr114572.C: New test.

    (cherry picked from commit 592536eb3c0a97a55b1019ff0216ef77e6ca847e)

  parent reply	other threads:[~2024-04-21  4:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-03  9:41 [Bug c++/114572] New: " j.reuter@fz-juelich.de
2024-04-03 11:28 ` [Bug c++/114572] " jakub at gcc dot gnu.org
2024-04-03 17:17 ` pinskia at gcc dot gnu.org
2024-04-04 14:49 ` jakub at gcc dot gnu.org
2024-04-05  7:34 ` cvs-commit at gcc dot gnu.org
2024-04-21  4:08 ` cvs-commit at gcc dot gnu.org [this message]
2024-04-23  6:45 ` jakub 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-114572-4-XRlsXCE1lW@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).