public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/106124] [11/12/13 Regression] ICE in dwarf2out_abstract_function, at dwarf2out.cc:23254
Date: Tue, 28 Mar 2023 14:58:46 +0000	[thread overview]
Message-ID: <bug-106124-4-IvvR40ZQ54@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106124-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #3)
> I suppose that's the OMP reduction function and that's always(?) inlined?

The reduction "function" is something artificial which holds some expressions
for the
OpenMP reductions; we just need to attach those statements to some decl for
name lookup purposes.
The problem is what to do with lambdas defined inside of those expressions, or
e.g. nested functions for the C case:
int q;

#pragma omp declare reduction (x : int : omp_out += omp_in + ({ int a = 1; void
foo () { a++; } foo (); a; }))

void bar (int *, int *);

void
foo ()
{
  int r = 0, s = 0;
  #pragma omp parallel reduction (x : r, s)
  bar (&r, &s);
}

ICEs too.  Lambdas are there certainly valid, we try to pretend the artificial
functions don't really exist for the debug info purposes, but apparently not
sufficiently.

  parent reply	other threads:[~2023-03-28 14:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28 17:11 [Bug c++/106124] New: " gscfq@t-online.de
2022-06-28 18:45 ` [Bug ipa/106124] " marxin at gcc dot gnu.org
2022-06-29  9:45 ` rguenth at gcc dot gnu.org
2022-06-29 11:23 ` jakub at gcc dot gnu.org
2023-03-27 14:37 ` rguenth at gcc dot gnu.org
2023-03-28 14:58 ` jakub at gcc dot gnu.org [this message]
2023-03-29  6:46 ` rguenther at suse dot de
2023-03-29  6:56 ` cvs-commit at gcc dot gnu.org
2023-03-29  6:57 ` [Bug ipa/106124] [11/12 " rguenth at gcc dot gnu.org
2023-04-17  9:14 ` cvs-commit at gcc dot gnu.org
2023-05-02 12:03 ` [Bug ipa/106124] [11 " cvs-commit at gcc dot gnu.org
2023-05-02 12:05 ` rguenth 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-106124-4-IvvR40ZQ54@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).