public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia 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 09:48:00 -0000	[thread overview]
Message-ID: <20100610094749.16180.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44492-87@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from pinskia at gcc dot gnu dot org  2010-06-10 09:47 -------
I think the real issue is that m is too generic from the point of the
documentation.

Reading:
http://gcc.gnu.org/onlinedocs/gcc-4.5.0/gcc/Simple-Constraints.html#Simple-Constraints

Makes it sound like it could accept an auto increment/decrement pattern.  While
using something like "o" would not.


-- 


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


  parent reply	other threads:[~2010-06-10  9:48 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 [this message]
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
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=20100610094749.16180.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).