public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marc.glisse at normalesup dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/52381] New: asm goto output operands Date: Sat, 25 Feb 2012 13:07:00 -0000 [thread overview] Message-ID: <bug-52381-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52381 Bug #: 52381 Summary: asm goto output operands Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: c AssignedTo: unassigned@gcc.gnu.org ReportedBy: marc.glisse@normalesup.org Hello, asm goto doesn't allow output operands (this is documented). I haven't found an enhancement request about it, but I think it is obvious that it is wanted. What I would like to ask in the meantime is for a more specific error message than: ex.c: In function 'h': ex.c:4:42: error: expected ':' before string constant or in the case of g++: ex.cc: In function 'void h(int)': ex.cc:4:42: error: expected ':' or '::' before string constant ex.cc:4:74: error: undefined named operand 'g_' Something like: "asm goto doesn't allow output operands" would be great. It took me a while to understand what was wrong by reading the doc, even with the nice column indication. silly example (yes, the contraints don't make sense, it doesn't matter) that gave the messages above: void f(int); void g(); void h(int i){ asm goto( "cmpl %1, %0\n\tje %l[g_]" : "+g" (i) : "i" (42) : "cc" : g_); return f(i); g_: return g(); }
next reply other threads:[~2012-02-25 12:57 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-25 13:07 marc.glisse at normalesup dot org [this message] 2012-02-27 9:24 ` [Bug c/52381] asm goto output operands diagnostics rguenth at gcc dot gnu.org 2012-02-27 21:13 ` marc.glisse at normalesup dot org 2013-01-10 13:49 ` timo.kreuzer at reactos dot org 2013-01-10 14:13 ` schwab@linux-m68k.org 2013-01-11 14:56 ` timo.kreuzer at reactos dot org 2023-01-25 22:27 ` 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-52381-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).