public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carl.nettelblad at it dot uu.se" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/99877] [8/9/10 Regression] Crash in GIMPLE pass:sanopt in huge function using OpenMP since r8-7544-gd838c2d5a8b1844c
Date: Mon, 12 Apr 2021 11:49:13 +0000 [thread overview]
Message-ID: <bug-99877-4-22aEokICvT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99877-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99877
--- Comment #7 from Carl Nettelblad <carl.nettelblad at it dot uu.se> ---
I solved the specific bug in my own code, but I had planned to use asan on that
codebase for quite a while, so the need to have some working compiler remains.
I'm not up to date on the planned release schedule. We get all major and minor
releases built for this cluster, but if 10.4 or 10.3.1 would be expected before
11.0 that would absolutely be a boon.
Hämta Outlook för Android<https://aka.ms/AAb9ysg>
________________________________
From: marxin at gcc dot gnu.org <gcc-bugzilla@gcc.gnu.org>
Sent: Monday, April 12, 2021 1:35:49 PM
To: carl.nettelblad@it.uu.se <carl.nettelblad@it.uu.se>
Subject: [Bug sanitizer/99877] [8/9/10 Regression] Crash in GIMPLE pass:sanopt
in huge function using OpenMP since r8-7544-gd838c2d5a8b1844c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99877
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[8/9/10/11 Regression] |[8/9/10 Regression] Crash
|Crash in GIMPLE pass:sanopt |in GIMPLE pass:sanopt in
|in huge function using |huge function using OpenMP
|OpenMP since |since
|r8-7544-gd838c2d5a8b1844c |r8-7544-gd838c2d5a8b1844c
Known to work| |11.0
--- Comment #6 from Martin Liška <marxin at gcc dot gnu.org> ---
Fixed on master so far.
@Carl: Are you interested in backport to GCC 10.x branch?
--
You are receiving this mail because:
You reported the bug.
När du har kontakt med oss på Uppsala universitet med e-post så innebär det att
vi behandlar dina personuppgifter. För att läsa mer om hur vi gör det kan du
läsa här: http://www.uu.se/om-uu/dataskydd-personuppgifter/
E-mailing Uppsala University means that we will process your personal data. For
more information on how this is performed, please read here:
http://www.uu.se/en/about-uu/data-protection-policy
next prev parent reply other threads:[~2021-04-12 11:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 20:57 [Bug sanitizer/99877] New: Crash in GIMPLE pass:sanopt in huge function using OpenMP carl.nettelblad at it dot uu.se
2021-04-01 21:33 ` [Bug sanitizer/99877] " carl.nettelblad at it dot uu.se
2021-04-02 8:14 ` marxin at gcc dot gnu.org
2021-04-02 9:29 ` [Bug sanitizer/99877] [8/9/10/11 Regression] Crash in GIMPLE pass:sanopt in huge function using OpenMP since r8-7544-gd838c2d5a8b1844c marxin at gcc dot gnu.org
2021-04-06 7:41 ` rguenth at gcc dot gnu.org
2021-04-12 8:51 ` marxin at gcc dot gnu.org
2021-04-12 11:34 ` cvs-commit at gcc dot gnu.org
2021-04-12 11:35 ` [Bug sanitizer/99877] [8/9/10 " marxin at gcc dot gnu.org
2021-04-12 11:49 ` carl.nettelblad at it dot uu.se [this message]
2021-04-12 11:53 ` jakub at gcc dot gnu.org
2021-04-12 12:17 ` marxin 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-99877-4-22aEokICvT@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).