public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gcc.hall at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/49611] Inline asm should support input/output of flags
Date: Fri, 17 Jul 2015 07:33:00 -0000	[thread overview]
Message-ID: <bug-49611-4-MlSDKlOTLz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49611-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49611

--- Comment #12 from Jeremy <gcc.hall at gmail dot com> ---
Hi David,
That's very interesting.  Its not in gcc 5.2.0 released yesterday though.
It probably does a setcc on x86 which doesn't really gain much, but on ARM
it could be useful.
More useful (as of gcc 5.0) is the new __builtin_xxx_overflow which uses
the overflow flag directly.   So for int16_t  operands for example:
    if(   __builtin_add_overflow( a, b, &result)  )
         printf( "overflow");
it would emit "addw; jno".

Jeremy



On 17 July 2015 at 06:41, gccbugzilla at limegreensocks dot com <
gcc-bugzilla@gcc.gnu.org> wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49611
>
> --- Comment #11 from David <gccbugzilla at limegreensocks dot com> ---
> Apparently this feature has been checked in:
> https://gcc.gnu.org/onlinedocs/gcc/Extended-Asm.html#FlagOutputOperands
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
>


  parent reply	other threads:[~2015-07-17  7:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-02  0:02 [Bug inline-asm/49611] New: " scovich at gmail dot com
2011-07-02 12:37 ` [Bug inline-asm/49611] " rguenth at gcc dot gnu.org
2011-07-04 20:32 ` scovich at gmail dot com
2012-04-12 16:39 ` scovich at gmail dot com
2012-06-28 16:06 ` jbemmel at zonnet dot nl
2014-05-30 11:38 ` gcc.hall at gmail dot com
2014-06-01 23:45 ` andi-gcc at firstfloor dot org
2014-06-02 11:29 ` scovich at gmail dot com
2015-07-17  5:21 ` gccbugzilla at limegreensocks dot com
2015-07-17  5:41 ` gccbugzilla at limegreensocks dot com
2015-07-17  7:33 ` gcc.hall at gmail dot com [this message]
2015-07-17 10:58 ` pinskia at gcc dot gnu.org
2015-07-17 21:24 ` gccbugzilla at limegreensocks dot com
2015-07-19 18:02 ` gcc.hall at gmail dot com
2015-07-20  9:05 ` gccbugzilla at limegreensocks dot com
2015-07-20  9:20 ` gcc.hall at gmail dot com

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-49611-4-MlSDKlOTLz@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).