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 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: Tue, 26 Sep 2023 18:05:52 +0000 [thread overview] Message-ID: <bug-110315-4-Ku9NG75TWA@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 #12 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-13 branch has been updated by Andrew Macleod <amacleod@gcc.gnu.org>: https://gcc.gnu.org/g:70639014a69cf50fe11dc1adbfe1db4c7760ce69 commit r13-7841-g70639014a69cf50fe11dc1adbfe1db4c7760ce69 Author: Andrew MacLeod <amacleod@redhat.com> Date: Tue Sep 26 09:44:39 2023 -0400 Reduce the initial size of int_range_max. This patch adds the ability to resize ranges as needed, defaulting to no resizing. int_range_max now defaults to 3 sub-ranges (instead of 255) and grows to 255 when the range being calculated does not fit. PR tree-optimization/110315 * value-range-storage.h (vrange_allocator::alloc_irange): Adjust new params. * value-range.cc (irange::operator=): Resize range. (irange::irange_union): Same. (irange::irange_intersect): Same. (irange::invert): Same. * value-range.h (irange::maybe_resize): New. (~int_range): New. (int_range_max): Default to 3 sub-ranges and resize as needed. (int_range::int_range): Adjust for resizing. (int_range::operator=): Same.
next prev parent reply other threads:[~2023-09-26 18:05 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 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 [this message] 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-Ku9NG75TWA@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).