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 18:57:22 +0000	[thread overview]
Message-ID: <bug-103395-4-dfTC5k0qhD@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

--- Comment #11 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Inline asm that only works with memory but in constraints says it accepts both
immediate constant and memory is IMNSHO just broken, it is just fine if the
compiler makes a different choice.
If "nor" with constant input on arm has meant actually just "or", then sure,
systemtap could be changed and after a couple of years it will propagate to all
stap copies used in the wild, but it is quite severe misoptimization of one of
the most common cases.  The systemtap macros don't really know what argument
will be passed to them, whether a constant, something that lives in memory,
something that lives in a register and ideally wants as few actual instructions
before those macros as possible to arrange the arguments so that debugger can
inspect them.

  parent reply	other threads:[~2021-11-24 18:57 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
2021-11-24 18:17 ` rearnsha at gcc dot gnu.org
2021-11-24 18:57 ` jakub at gcc dot gnu.org [this message]
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-dfTC5k0qhD@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).