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 middle-end/105032] Compiling inline ASM x86 causing GCC stuck in an endless loop with 100% CPU usage Date: Wed, 23 Mar 2022 09:24:23 +0000 [thread overview] Message-ID: <bug-105032-4-wkBS0CFYHo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105032-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105032 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2022-03-23 Status|UNCONFIRMED |NEW Ever confirmed|0 |1 CC| |jakub at gcc dot gnu.org, | |vmakarov at gcc dot gnu.org --- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> --- This has been hanging or ICEing on and off since forever. E.g. even r105000 ICEs, r200000 works, r210000 ICEs, r10-5912 works, r11-1 hangs, so does current trunk. The first revision after r10-5912 to start hanging was r10-6326-gbcf3fa7cf5a3d024b507. Note, without optimizations, the inline asm is on or beyond the border what can be handled, it uses 6 of the 8 GPRs the arch has, the further two are the stack pointer and when not optimizing or if frame pointer is for whatever reason needed frame pointer. The asm also has a memory input. So, it fully depends on optimization (which isn't done with -O0 generally) that the address of the _arg6 variable can be expressed as offset(%esp) or offset(%ebp). If it is not (and -O0 asks for no optimizations), then there are no registers left how to describe the input.
next prev parent reply other threads:[~2022-03-23 9:24 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-23 3:46 [Bug c/105032] New: " ammarfaizi2 at gmail dot com 2022-03-23 3:52 ` [Bug middle-end/105032] " pinskia at gcc dot gnu.org 2022-03-23 4:05 ` crazylht at gmail dot com 2022-03-23 9:24 ` jakub at gcc dot gnu.org [this message] 2022-03-23 9:28 ` jakub at gcc dot gnu.org 2022-03-23 13:22 ` ammarfaizi2 at gmail dot com 2022-03-23 13:27 ` ammarfaizi2 at gmail dot com 2022-03-23 13:50 ` jakub at gcc dot gnu.org 2022-03-23 19:24 ` hjl.tools at gmail dot com 2022-03-29 12:49 ` vmakarov at gcc dot gnu.org 2022-03-30 17:02 ` vmakarov at gcc dot gnu.org 2022-03-30 17:10 ` cvs-commit at gcc dot gnu.org 2022-03-30 17:12 ` vmakarov at gcc dot gnu.org 2022-04-01 14:21 ` cvs-commit at gcc dot gnu.org 2022-07-28 18:43 ` hjl.tools at gmail dot com 2022-08-02 6:18 ` andrey.vihrov at gmail 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-105032-4-wkBS0CFYHo@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).