public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hpa at zytor dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/59615] New: "asm goto" output or at least clobbered operands Date: Sat, 28 Dec 2013 00:23:00 -0000 [thread overview] Message-ID: <bug-59615-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59615 Bug ID: 59615 Summary: "asm goto" output or at least clobbered operands Product: gcc Version: unknown Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: hpa at zytor dot com There are a number of uses of "asm goto" which requires at least on dyadic architectures like x86 the ability to clobber an operand. However, the current definition of "asm goto" doesn't allow any output operands, and the clobber list only works on specific registers (which are generally not allowed to be inputs, anyway.) For example: asm goto("add %1,%0 ; " "jc %l[t_err] ; " "cmp %2,%0 ; " "ja %l[t_err] ; " : "+r" (addr) : "g" (size), "g" (limit) : : t_err); return false; t_err: return true; This is part of a proposed implementation of access_ok(), a limit test with a guard for wraparound, used heavily in the Linux kernel. There needs to be a way to communicate to gcc that "addr" is clobbered by the first instruction.
next reply other threads:[~2013-12-28 0:23 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-12-28 0:23 hpa at zytor dot com [this message] 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 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@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).