public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/103910] openjdk17 causes ICE on -O3 -march=opteron -fcheck-new: during GIMPLE pass: aprefetch: in gimple_build_call, at gimple.c:267
Date: Tue, 01 Feb 2022 22:18:58 +0000	[thread overview]
Message-ID: <bug-103910-4-gusq3ynT5d@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103910-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #12 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Sam James from comment #11)
> (In reply to Andrew Pinski from comment #10)
> > Someone would have hit this a long time ago, in GCC 4.3.0 or latter.
> 
> My point was that some software has recently started building with PCH by
> default and hence it's only appeared now and I was surprised at the number
> of people who were affected. I understand the bug isn't new, it's just been
> exposed by a change in the ecosystem.

Could you provide some more info on the software that has recently started
building with PCH by default? There has been some talk of wanting to rip PCH
out of GCC at some point, but if there's software out there actually depending
on it, that could be useful info for the argument that PCH ought to be kept.

  parent reply	other threads:[~2022-02-01 22:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-04 22:30 [Bug c++/103910] New: openjdk17 causes ICE on -O3 -march=opteron -fchecking-new: " slyfox at gcc dot gnu.org
2022-01-04 22:35 ` [Bug target/103910] " pinskia at gcc dot gnu.org
2022-01-04 22:35 ` slyfox at gcc dot gnu.org
2022-01-04 22:37 ` pinskia at gcc dot gnu.org
2022-01-05  8:37 ` slyfox at gcc dot gnu.org
2022-01-05 21:11 ` [Bug target/103910] openjdk17 causes ICE on -O3 -march=opteron -fcheck-new: " pinskia at gcc dot gnu.org
2022-01-05 22:38 ` cvs-commit at gcc dot gnu.org
2022-01-05 22:41 ` pinskia at gcc dot gnu.org
2022-01-07 15:34 ` sam at gentoo dot org
2022-01-07 15:35 ` sam at gentoo dot org
2022-01-07 22:45 ` pinskia at gcc dot gnu.org
2022-01-08  0:20 ` sam at gentoo dot org
2022-02-01 22:18 ` egallager at gcc dot gnu.org [this message]
2024-02-07  2:27 ` alx at kernel dot 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-103910-4-gusq3ynT5d@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).