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 rtl-optimization/112610] [12/13/14 Regression] ICE: SIGSEGV with -flive-range-shrinkage -fdump-rtl-all-all -fira-verbose=9
Date: Wed, 22 Nov 2023 14:04:42 +0000	[thread overview]
Message-ID: <bug-112610-4-L7U3reP7qA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112610-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Vladimir Makarov <vmakarov@gcc.gnu.org>:

https://gcc.gnu.org/g:95f61de95bbcc2e4fb7020e27698140abea23788

commit r14-5757-g95f61de95bbcc2e4fb7020e27698140abea23788
Author: Vladimir N. Makarov <vmakarov@redhat.com>
Date:   Wed Nov 22 09:01:02 2023 -0500

    [IRA]: Fix using undefined dump file in IRA code during insn scheduling

    Part of IRA code is used for register pressure sensitive insn
    scheduling and live range shrinkage.  Numerous changes of IRA resulted
    in that this IRA code uses dump file passed by the scheduler and
    internal ira dump file (in called functions) which can be undefined or
    freed by the scheduler during compiling previous functions.  The patch
    fixes this problem.  To reproduce the error valgrind should be used
    and GCC should be compiled with valgrind annotations.  Therefor the
    patch does not contain the test case.

    gcc/ChangeLog:

            PR rtl-optimization/112610
            * ira-costs.cc: (find_costs_and_classes): Remove arg.
            Use ira_dump_file for printing.
            (print_allocno_costs, print_pseudo_costs): Ditto.
            (ira_costs): Adjust call of find_costs_and_classes.
            (ira_set_pseudo_classes): Set up and restore ira_dump_file.

  parent reply	other threads:[~2023-11-22 14:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-18 20:24 [Bug rtl-optimization/112610] New: " zsojka at seznam dot cz
2023-11-20  9:30 ` [Bug rtl-optimization/112610] " rguenth at gcc dot gnu.org
2023-11-22 14:04 ` cvs-commit at gcc dot gnu.org [this message]
2024-03-07 21:01 ` law at gcc dot gnu.org
2024-03-09 17:13 ` law 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-112610-4-L7U3reP7qA@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).