public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ed.gcc at pobox dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/100102] [9/10/11/12 Regression] ICE in tsubst, at cp/pt.c:15310
Date: Fri, 04 Jun 2021 21:44:49 +0000	[thread overview]
Message-ID: <bug-100102-4-AFUfFDvSxV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100102-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #21 from Eduard Rozenberg <ed.gcc at pobox dot com> ---
@ppalka Huge thanks for this fix - it's working well for me. Very happy to see
the patch applied with no problems to gcc 10.3.0, because it could take several
years until the OS and Nvidia support gcc 11 or 12. Otherwise I would have had
to move back to gcc 10.2.0 and build custom kernels for quite some time.

Tested as follows:
* Rebuilt Slackware gcc 10.3.0 packages with the patch for `pt.c`
* Built Nvidia nccl-tests - build succeeded (was failing before the patch)
* Built latest pytorch git with Nvidia support - build succeeded (was failing
before the patch)

  parent reply	other threads:[~2021-06-04 21:44 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-15 16:03 [Bug tree-optimization/100102] New: " schnetter at gmail dot com
2021-04-15 16:05 ` [Bug tree-optimization/100102] " schnetter at gmail dot com
2021-04-15 17:37 ` jakub at gcc dot gnu.org
2021-04-15 17:41 ` [Bug tree-optimization/100102] [8/9/10/11 Regression] " jakub at gcc dot gnu.org
2021-04-15 18:13 ` jakub at gcc dot gnu.org
2021-04-16  6:57 ` rguenth at gcc dot gnu.org
2021-04-16 13:01 ` schnetter at gmail dot com
2021-04-28  1:26 ` [Bug tree-optimization/100102] [8/9/10/11/12 " ed.gcc at pobox dot com
2021-04-28 12:05 ` [Bug c++/100102] " ppalka at gcc dot gnu.org
2021-04-28 14:56 ` taraba.peter at mail dot com
2021-05-14  9:54 ` [Bug c++/100102] [9/10/11/12 " jakub at gcc dot gnu.org
2021-06-01  8:20 ` rguenth at gcc dot gnu.org
2021-06-03 16:50 ` redi at gcc dot gnu.org
2021-06-03 16:52 ` redi at gcc dot gnu.org
2021-06-03 16:53 ` redi at gcc dot gnu.org
2021-06-03 16:55 ` redi at gcc dot gnu.org
2021-06-03 17:02 ` redi at gcc dot gnu.org
2021-06-03 23:14 ` ppalka at gcc dot gnu.org
2021-06-04  2:32 ` ppalka at gcc dot gnu.org
2021-06-04  3:50 ` ppalka at gcc dot gnu.org
2021-06-04 17:47 ` cvs-commit at gcc dot gnu.org
2021-06-04 21:44 ` ed.gcc at pobox dot com [this message]
2021-06-07 14:22 ` ppalka at gcc dot gnu.org
2021-06-07 22:37 ` cvs-commit at gcc dot gnu.org
2021-06-07 22:54 ` cvs-commit at gcc dot gnu.org
2021-06-07 22:56 ` [Bug c++/100102] [9 " ppalka at gcc dot gnu.org
2021-06-08  3:55 ` cvs-commit at gcc dot gnu.org
2021-11-03 18:38 ` ppalka at gcc dot gnu.org
2021-12-02 19:20 ` ppalka 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-100102-4-AFUfFDvSxV@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).