public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/109137] [12/13 regression] Compiling ffmpeg with -m32 on x86_64-pc-linux-gnu hangs on libavcodec/h264_cabac.c since r12-9086-g489c81db7d4f75 Date: Thu, 16 Mar 2023 10:22:05 +0000 [thread overview] Message-ID: <bug-109137-4-qynqi4Wa0z@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109137-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109137 --- Comment #12 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Ah, but 1690 if (flag_checking 1691 && (lra_assignment_iter_after_spill 1692 > LRA_MAX_ASSIGNMENT_ITERATION_NUMBER)) 1693 internal_error 1694 ("maximum number of LRA assignment passes is achieved (%d)", 1695 LRA_MAX_ASSIGNMENT_ITERATION_NUMBER); is guarded with -fchecking. So it really hangs with -fno-checking. Now, on the error: ‘asm’ operand has impossible constraints errors the problematic insns are removed: 1864 PATTERN (insn) = gen_rtx_USE (VOIDmode, const0_rtx); 1865 lra_set_insn_deleted (insn); or nulified in case of asm goto, so wonder whether some LRA state shouldn't be reset at that point as well or what is the reason for the > 30 iterations.
next prev parent reply other threads:[~2023-03-16 10:22 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-15 0:30 [Bug c/109137] New: " sam at gentoo dot org 2023-03-15 0:31 ` [Bug c/109137] " sam at gentoo dot org 2023-03-15 0:33 ` sam at gentoo dot org 2023-03-15 0:38 ` [Bug target/109137] " pinskia at gcc dot gnu.org 2023-03-15 0:40 ` pinskia at gcc dot gnu.org 2023-03-15 0:44 ` pinskia at gcc dot gnu.org 2023-03-15 0:58 ` sam at gentoo dot org 2023-03-15 1:06 ` pinskia at gcc dot gnu.org 2023-03-15 8:38 ` rguenth at gcc dot gnu.org 2023-03-15 8:42 ` pinskia at gcc dot gnu.org 2023-03-15 9:00 ` rguenther at suse dot de 2023-03-16 10:03 ` jakub at gcc dot gnu.org 2023-03-16 10:22 ` jakub at gcc dot gnu.org [this message] 2023-03-16 10:41 ` rguenther at suse dot de 2023-03-16 10:58 ` jakub at gcc dot gnu.org 2023-03-21 14:56 ` vmakarov at gcc dot gnu.org 2023-03-22 17:36 ` cvs-commit at gcc dot gnu.org 2023-03-23 16:25 ` jakub at gcc dot gnu.org 2023-03-23 18:15 ` [Bug target/109137] [12 " jakub at gcc dot gnu.org 2023-03-24 8:45 ` cvs-commit at gcc dot gnu.org 2023-03-24 13:10 ` vmakarov at gcc dot gnu.org 2023-03-30 15:16 ` hubicka at gcc dot gnu.org 2023-03-30 15:32 ` jakub at gcc dot gnu.org 2023-03-31 7:21 ` rguenther at suse dot de 2023-04-05 1:06 ` sjames at gcc dot gnu.org 2023-04-14 17:20 ` cvs-commit at gcc dot gnu.org 2023-04-14 17:23 ` hubicka at gcc dot gnu.org 2023-04-17 10:56 ` rguenth at gcc dot gnu.org 2023-05-08 12:26 ` rguenth at gcc dot gnu.org 2024-06-12 11:36 ` [Bug target/109137] " rguenth 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-109137-4-qynqi4Wa0z@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).