public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bouanto at zoho dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug jit/87291] Add support for inline asm to libgccjit
Date: Sat, 06 Jun 2020 01:04:02 +0000 [thread overview]
Message-ID: <bug-87291-4-53OhVTk5Hc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-87291-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87291
--- Comment #23 from bouanto at zoho dot com ---
Created attachment 48685
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48685&action=edit
Example of global assembly
See answers below.
(In reply to David Malcolm from comment #22)
> Created attachment 48684 [details]
> Updated work-in-progress patch which adds "asm goto" support
>
> Here's an updated version of the patch which adds "asm goto" support. grep
> for test_i386_basic_asm_3a to see an example.
>
> Also uploaded to:
> https://dmalcolm.fedorapeople.org/gcc/2020-06-05/0001-FIXME-WIP-on-extended-
> asm-support-v2.patch
>
> Does this API make sense?
Yes, now I understand what you meant.
The API looks good.
> I could use a concrete example of what you might use in C.
> An issue is ordering: in C, these top-level statements presumably are ordered
> relative to each other and the function bodies, based on the order they're seen
> by the parser (though I'm guessing here). Would something similar happen based
> on the order of calls to gcc_jit_context_new_function?
I attached an example of global assembly.
I don't understand the ordering issue.
I also don't understand how gcc_jit_context_new_function is used here.
next prev parent reply other threads:[~2020-06-06 1:04 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-87291-4@http.gcc.gnu.org/bugzilla/>
2020-06-03 12:54 ` bouanto at zoho dot com
2020-06-03 13:48 ` dmalcolm at gcc dot gnu.org
2020-06-03 21:53 ` bouanto at zoho dot com
2020-06-03 22:05 ` pinskia at gcc dot gnu.org
2020-06-03 22:09 ` bouanto at zoho dot com
2020-06-03 22:44 ` dmalcolm at gcc dot gnu.org
2020-06-03 22:55 ` dmalcolm at gcc dot gnu.org
2020-06-03 23:11 ` bouanto at zoho dot com
2020-06-04 1:05 ` programmerjake at gmail dot com
2020-06-04 1:08 ` programmerjake at gmail dot com
2020-06-04 1:42 ` bouanto at zoho dot com
2020-06-04 14:18 ` dmalcolm at gcc dot gnu.org
2020-06-04 14:21 ` dmalcolm at gcc dot gnu.org
2020-06-04 14:24 ` bouanto at zoho dot com
2020-06-04 21:01 ` dmalcolm at gcc dot gnu.org
2020-06-04 21:03 ` dmalcolm at gcc dot gnu.org
2020-06-05 0:09 ` bouanto at zoho dot com
2020-06-05 15:32 ` dmalcolm at gcc dot gnu.org
2020-06-05 15:37 ` bouanto at zoho dot com
2020-06-05 16:24 ` dmalcolm at gcc dot gnu.org
2020-06-05 16:32 ` dmalcolm at gcc dot gnu.org
2020-06-06 1:04 ` bouanto at zoho dot com [this message]
2020-06-06 8:56 ` dmalcolm at gcc dot gnu.org
2020-06-06 11:19 ` bouanto at zoho dot com
2020-06-06 16:37 ` dmalcolm at gcc dot gnu.org
2020-06-06 17:34 ` dmalcolm at gcc dot gnu.org
2020-06-06 17:41 ` dmalcolm at gcc dot gnu.org
2020-06-06 22:59 ` bouanto at zoho dot com
2020-06-08 14:11 ` dmalcolm at gcc dot gnu.org
2020-06-08 14:12 ` dmalcolm at gcc dot gnu.org
2020-06-08 14:56 ` bouanto at zoho dot com
2020-11-12 22:42 ` dmalcolm 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-87291-4-53OhVTk5Hc@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).