public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jbemmel at zonnet dot nl" <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: Thu, 28 Jun 2012 16:06:00 -0000 [thread overview] Message-ID: <bug-49611-4-sUny4W2KHW@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49611-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49611 Jeroen van Bemmel <jbemmel at zonnet dot nl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jbemmel at zonnet dot nl --- Comment #4 from Jeroen van Bemmel <jbemmel at zonnet dot nl> 2012-06-28 16:06:18 UTC --- Ideally, there would be some way to express that a given asm goto block depends on the flags, to prevent GCC from reordering flags-changing instructions and breaking the code. As a compromise, GCC could simply assume by default that asm goto blocks depend on the flags. Like Ryan, I believe that most people using asm goto would use it for such a purpose, and any missed optimization opportunities are a small price to pay for correct code.
next prev parent reply other threads:[~2012-06-28 16:06 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 [this message] 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 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-sUny4W2KHW@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: linkBe 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).