public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/44492] auto-inc-dec pushes PRE_MODIFY/PRE_INC into inline asm operands
Date: Thu, 10 Jun 2010 15:23:00 -0000	[thread overview]
Message-ID: <20100610152217.28792.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44492-87@http.gcc.gnu.org/bugzilla/>



------- Comment #20 from jakub at gcc dot gnu dot org  2010-06-10 15:22 -------
Another option is to disallow side-effects in inline asm memory operands and
let the user explicitly request that the side-effects are possible, through
some new constraint modifier (e.g. _ used as "_mi" or "=_g" would tell
auto-inc-dec it can put side-effects into it).  When _ is present, the user
would promise that the mem operand is used exactly once in an insn that is
executed exactly once in that inline asm and that any target dependent
modifiers
that are needed for auto-update insns are used too (%P on ia64, %U on ppc,
etc.).


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44492


  parent reply	other threads:[~2010-06-10 15:23 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-10  9:31 [Bug middle-end/44492] New: " jakub at gcc dot gnu dot org
2010-06-10  9:34 ` [Bug middle-end/44492] " pinskia at gcc dot gnu dot org
2010-06-10  9:45 ` jakub at gcc dot gnu dot org
2010-06-10  9:48 ` pinskia at gcc dot gnu dot org
2010-06-10 10:12 ` schwab at linux-m68k dot org
2010-06-10 10:25 ` jakub at gcc dot gnu dot org
2010-06-10 10:59 ` schwab at linux-m68k dot org
2010-06-10 11:06 ` schwab at linux-m68k dot org
2010-06-10 11:37 ` jakub at gcc dot gnu dot org
2010-06-10 11:51 ` schwab at linux-m68k dot org
2010-06-10 12:11 ` fche at redhat dot com
2010-06-10 12:25 ` jakub at gcc dot gnu dot org
2010-06-10 12:27 ` matz at gcc dot gnu dot org
2010-06-10 12:39 ` schwab at linux-m68k dot org
2010-06-10 12:43 ` schwab at linux-m68k dot org
2010-06-10 12:46 ` schwab at linux-m68k dot org
2010-06-10 13:24 ` fche at redhat dot com
2010-06-10 13:34 ` matz at gcc dot gnu dot org
2010-06-10 15:11 ` schwab at linux-m68k dot org
2010-06-10 15:19 ` schwab at linux-m68k dot org
2010-06-10 15:23 ` jakub at gcc dot gnu dot org [this message]
2010-06-10 17:07 ` jakub at gcc dot gnu dot org
2010-06-11 13:23 ` jakub at gcc dot gnu dot org
2010-06-24 17:48 ` jakub at gcc dot gnu dot org
2010-08-13 12:48 ` jakub at gcc dot gnu dot 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=20100610152217.28792.qmail@sourceware.org \
    --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).