public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amacleod at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/110315] [13 Regression] g++ crashes with a segmentation fault while compiling a large const std::vector of std::string since r13-6566-ge0324e2629e25a90 Date: Wed, 19 Jul 2023 19:29:11 +0000 [thread overview] Message-ID: <bug-110315-4-WGrcrLkdy2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110315-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110315 --- Comment #6 from Andrew Macleod <amacleod at redhat dot com> --- I think the difference is actually Aldys work to reduce the size of Value_Range rather than other stack saving changes. I think I can make some adjustments so that our usage of Value_Range are on leaf functions in some places instead of remaining in the call chain. I'll get back to you
next prev parent reply other threads:[~2023-07-19 19:29 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-19 23:34 [Bug c++/110315] New: " glebfm at altlinux dot org 2023-06-20 0:02 ` [Bug tree-optimization/110315] " pinskia at gcc dot gnu.org 2023-07-19 11:34 ` rguenth at gcc dot gnu.org 2023-07-19 14:06 ` amacleod at redhat dot com 2023-07-19 18:12 ` amacleod at redhat dot com 2023-07-19 18:55 ` amacleod at redhat dot com 2023-07-19 19:29 ` amacleod at redhat dot com [this message] 2023-07-20 15:07 ` amacleod at redhat dot com 2023-07-27 9:26 ` rguenth at gcc dot gnu.org 2023-07-29 7:07 ` glebfm at altlinux dot org 2023-09-26 11:03 ` rguenth at gcc dot gnu.org 2023-09-26 13:14 ` amacleod at redhat dot com 2023-09-26 18:05 ` cvs-commit at gcc dot gnu.org 2023-09-26 18:06 ` amacleod at redhat dot com
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-110315-4-WGrcrLkdy2@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: linkBe 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).