public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/59615] "asm goto" output or at least clobbered operands
Date: Mon, 30 Dec 2013 18:17:00 -0000	[thread overview]
Message-ID: <bug-59615-4-iQ3LftTAvv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59615-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from Marc Glisse <glisse at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #7)
> They are modelled in the .md files now, we just don't have general purpose
> builtins for this yet in GCC 4.9, it is only used for -fsanitize=undefined
> right now.

Ah, right, I thought you had only added an expander, nice that it is properly
modeled now (thanks), though I am yet to find C code where combine (or other)
ends up matching this pattern, which seems doable without a builtin. (well, we
are still losing the high half of the product if we use that pattern, but
that's less often needed)

Sorry for the hijack, back to comment 5 as the real motivation.


  parent reply	other threads:[~2013-12-30 18:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-28  0:23 [Bug c/59615] New: " hpa at zytor dot com
2013-12-28  8:42 ` [Bug c/59615] " jakub at gcc dot gnu.org
2013-12-28 10:29 ` ubizjak at gmail dot com
2013-12-28 16:28 ` jakub at gcc dot gnu.org
2013-12-30  1:37 ` hpa at zytor dot com
2013-12-30 17:53 ` glisse at gcc dot gnu.org
2013-12-30 17:56 ` jakub at gcc dot gnu.org
2013-12-30 18:17 ` glisse at gcc dot gnu.org [this message]
2021-09-01  1:05 ` [Bug inline-asm/59615] " pinskia 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-59615-4-iQ3LftTAvv@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).