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: Fri, 29 May 2020 08:50:25 +0000 [thread overview]
Message-ID: <bug-95315-4-LMW1E62QHd@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 #6 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:3d0675f3bb54b58903bc9214d05c8e6d20e5f313
commit r11-712-g3d0675f3bb54b58903bc9214d05c8e6d20e5f313
Author: Jakub Jelinek <jakub@redhat.com>
Date: Fri May 29 10:48:40 2020 +0200
openmp: One omp_resolve_declare_variant followup
As noticed by Arseny, I got the condition when to call the add removal hook
wrong wrong. Fixed thusly.
2020-05-28 Jakub Jelinek <jakub@redhat.com>
PR middle-end/95315
* omp-general.c (omp_resolve_declare_variant): Fix up addition of
declare variant cgraph node removal callback.
* gcc.dg/gomp/pr95315-2.c: New test.
next prev parent reply other threads:[~2020-05-29 8:50 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
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 [this message]
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-LMW1E62QHd@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).