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 middle-end/95315] [11 Regression] ICE: Segmentation fault (in lookup_page_table_entry) since r11-382-g7a50e7087567cffb
Date: Wed, 27 May 2020 08:30:18 +0000	[thread overview]
Message-ID: <bug-95315-4-zR6bI1IvME@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95315-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:baff22c48bdee9cb644b7336bf6f20f799531507

commit r11-653-gbaff22c48bdee9cb644b7336bf6f20f799531507
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Wed May 27 10:25:56 2020 +0200

    openmp: Fix up omp_declare_variant{s,_alt} htab handling

    This patch fixes a GC ICE.  During debugging, I've found that during
    gimplification we can actually call omp_resolve_declare_variant multiple
    times and it would create a new magic declare_variant_alt FUNCTION_DECL
    each time, which is undesirable, once we have such a decl, we should just
    use that.  The other problem is that there was no cgraph node removal hook.
    As the omp_declare_variants htab is used just early during gimplification,
    we can just clear the whole htab, rather than trying to lookup and remove
    a particular entry.  The other hash table is used later as well and that
    one uses just DECL_UID as hash, so in that case the patch removes the elt.

    2020-05-27  Jakub Jelinek  <jakub@redhat.com>

            PR middle-end/95315
            * omp-general.c (omp_declare_variant_remove_hook): New function.
            (omp_resolve_declare_variant): Always return base if it is already
            declare_variant_alt magic decl itself.  Register
            omp_declare_variant_remove_hook as cgraph node removal hook.

            * gcc.dg/gomp/pr95315.c: New test.

  parent reply	other threads:[~2020-05-27  8:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-25 14:37 [Bug middle-end/95315] New: [11 Regression] ICE: Segmentation fault (in lookup_page_table_entry) asolokha at gmx dot com
2020-05-25 14:46 ` [Bug middle-end/95315] " rguenth at gcc dot gnu.org
2020-05-26  7:21 ` [Bug middle-end/95315] [11 Regression] ICE: Segmentation fault (in lookup_page_table_entry) since r11-382-g7a50e7087567cffb marxin at gcc dot gnu.org
2020-05-26 11:50 ` jakub at gcc dot gnu.org
2020-05-27  8:30 ` cvs-commit at gcc dot gnu.org [this message]
2020-05-27 10:53 ` asolokha at gmx dot com
2020-05-27 10:57 ` jakub at gcc dot gnu.org
2020-05-29  8:50 ` cvs-commit at gcc dot gnu.org
2020-05-29  9:42 ` 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-95315-4-zR6bI1IvME@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).