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/103395] [9/10/11/12 Regression] ICE on qemu in arm create_fix_barrier
Date: Wed, 24 Nov 2021 16:52:48 +0000 [thread overview]
Message-ID: <bug-103395-4-LFD3OLQdT5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103395-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103395
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fche at redhat dot com
--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
CCing Frank as this is systemtap sys/sdt.h
which has:
# ifndef STAP_SDT_ARG_CONSTRAINT
# if defined __powerpc__
# define STAP_SDT_ARG_CONSTRAINT nZr
# else
# define STAP_SDT_ARG_CONSTRAINT nor
# endif
# endif
All of n, o and r are generic constraints and const0_rtx is valid for the "n"
constraint, so why is the backend trying to put it into memory at all?
What is systemtap trying to do is not use those operands in any instruction,
but note for the debugger how to find out the value of the asm input operand
(read some register, some memory or the immediate constant).
next prev parent reply other threads:[~2021-11-24 16:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 19:32 [Bug target/103395] New: " jakub at gcc dot gnu.org
2021-11-23 19:33 ` [Bug target/103395] " jakub at gcc dot gnu.org
2021-11-23 22:07 ` rjones at redhat dot com
2021-11-24 9:32 ` pinskia at gcc dot gnu.org
2021-11-24 9:40 ` jakub at gcc dot gnu.org
2021-11-24 12:16 ` rearnsha at gcc dot gnu.org
2021-11-24 12:25 ` jakub at gcc dot gnu.org
2021-11-24 13:05 ` rearnsha at gcc dot gnu.org
2021-11-24 13:18 ` jakub at gcc dot gnu.org
2021-11-24 16:35 ` rearnsha at gcc dot gnu.org
2021-11-24 16:52 ` jakub at gcc dot gnu.org [this message]
2021-11-24 18:17 ` rearnsha at gcc dot gnu.org
2021-11-24 18:57 ` jakub at gcc dot gnu.org
2021-11-24 18:58 ` jakub at gcc dot gnu.org
2021-11-25 10:03 ` fw at gcc dot gnu.org
2021-11-25 10:16 ` jakub at gcc dot gnu.org
2021-11-25 11:11 ` jakub at gcc dot gnu.org
2021-11-25 11:25 ` jakub at gcc dot gnu.org
2021-11-26 9:38 ` berrange at redhat dot com
2021-11-26 13:46 ` jakub at gcc dot gnu.org
2022-05-27 9:46 ` [Bug target/103395] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:47 ` jakub at gcc dot gnu.org
2023-07-07 10:41 ` [Bug target/103395] [11/12/13/14 " 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-103395-4-LFD3OLQdT5@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).