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/94172] [arm-none-eabi] ICE in expand_debug_locations, at cfgexpand.c:5403 Date: Mon, 16 Mar 2020 16:34:13 +0000 [thread overview] Message-ID: <bug-94172-4-FmfdRLcZHc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94172-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94172 --- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Oops, sorry, I've used __asm volatile (""); so that it doesn't have an arm specific instruction and in that case it doesn't ICE. With __asm volatile ("nop"); it ICEs even on x86_64-linux. Looking...
next prev parent reply other threads:[~2020-03-16 16:34 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-14 3:27 [Bug middle-end/94172] New: " dtaubert at atmosic dot com 2020-03-14 3:46 ` [Bug middle-end/94172] " pinskia at gcc dot gnu.org 2020-03-16 15:55 ` wilco at gcc dot gnu.org 2020-03-16 16:25 ` jakub at gcc dot gnu.org 2020-03-16 16:30 ` rearnsha at gcc dot gnu.org 2020-03-16 16:34 ` jakub at gcc dot gnu.org [this message] 2020-03-16 16:35 ` wilco at gcc dot gnu.org 2020-03-16 16:39 ` tnfchris at gcc dot gnu.org 2020-03-16 16:46 ` jakub at gcc dot gnu.org 2020-03-16 18:21 ` [Bug c/94172] " jakub at gcc dot gnu.org 2020-03-17 21:33 ` cvs-commit at gcc dot gnu.org 2020-03-18 7:55 ` jakub at gcc dot gnu.org 2020-04-07 19:03 ` cvs-commit at gcc dot gnu.org 2020-09-17 14:25 ` cvs-commit at gcc dot gnu.org 2020-09-17 17:19 ` 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-94172-4-FmfdRLcZHc@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).