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 target/99104] [11 Regression] ICE: Segmentation fault (in bitmap_list_find_element)
Date: Thu, 18 Feb 2021 08:22:30 +0000	[thread overview]
Message-ID: <bug-99104-4-8IUZu526pA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99104-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:decd8fb0128870d0d768ba53dae626913d6d9c54

commit r11-7274-gdecd8fb0128870d0d768ba53dae626913d6d9c54
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Thu Feb 18 09:16:28 2021 +0100

    i386: Fix up df uses in i386 splitters [PR99104]

    The following testcase started ICEing with my recent changes to enable
    split4 after sel-sched, but it seems the bug is more general.
    Some of the i386 splitter condition functions use and rely on df, but
    the split passes don't really df_analyze/df_finish_pass, so the DF info
    may be stale or not computed at all - the particular ICE is because
    there is a new bb and df_get_live_out (bb) returns NULL on it as the
    live or lr problem has not been computed yet.

    This patch fixes it by not calling ix86_ok_to_clobber_flags from
    ix86_avoid_lea_for_add where it wasn't ever needed because the splitters
    using that function as condition have (clobber FLAGS) in their pattern.
    And, changes the ix86_avoid_lea_for_addr using splitter from normal
splitter
    to peephole2 splitter that uses peep2_regno_dead_p infrastructure to
    determine if FLAGS is dead.  Also, it saves and restores recog_data
    variable around the call to distance_non_agu_define and doesn't call
    extract_insn_data there, because split_insns or peephole2_insns just
    clear recog_data.insn and then fill in recog_data.operand array, and so
    might not match what extract_insn will do on the insn at all.

    2021-02-18  Jakub Jelinek  <jakub@redhat.com>

            PR target/99104
            * config/i386/i386.c (distance_non_agu_define): Don't call
            extract_insn_cached here.
            (ix86_lea_outperforms): Save and restore recog_data around call
            to distance_non_agu_define and distance_agu_use.
            (ix86_ok_to_clobber_flags): Remove.
            (ix86_avoid_lea_for_add): Don't call ix86_ok_to_clobber_flags.
            (ix86_avoid_lea_for_addr): Likewise.  Adjust function comment.
            * config/i386/i386.md (*lea<mode>): Change from
define_insn_and_split
            into define_insn.  Move the splitting to define_peephole2 and
            check there using peep2_regno_dead_p if FLAGS_REG is dead.

            * gcc.dg/pr99104.c: New test.

  parent reply	other threads:[~2021-02-18  8:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-15 11:32 [Bug target/99104] New: " asolokha at gmx dot com
2021-02-15 12:06 ` [Bug target/99104] " jakub at gcc dot gnu.org
2021-02-15 12:52 ` jakub at gcc dot gnu.org
2021-02-15 14:46 ` rguenth at gcc dot gnu.org
2021-02-15 15:31 ` jakub at gcc dot gnu.org
2021-02-15 16:59 ` jakub at gcc dot gnu.org
2021-02-18  8:22 ` cvs-commit at gcc dot gnu.org [this message]
2021-02-18  8:35 ` jakub 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-99104-4-8IUZu526pA@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).