public inbox for jit@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Li, Yicheng" <yli137@vols.utk.edu>
To: David Malcolm <dmalcolm@redhat.com>
Cc: "jit@gcc.gnu.org" <jit@gcc.gnu.org>
Subject: Re: Libgccjit citation
Date: Mon, 7 Aug 2023 17:23:59 +0000	[thread overview]
Message-ID: <09823122-B031-4BAC-B9F0-471BD04A21C2@vols.utk.edu> (raw)
In-Reply-To: <eddd782cdbc7b69a25d5318c9174c8163e5466a6.camel@redhat.com>


[-- Attachment #1.1: Type: text/plain, Size: 1216 bytes --]

Hi,

Here’s the draft and it’s due tonight.
I’ll see how I can cite this.

Thank you
Yicheng Li


> On Aug 7, 2023, at 1:20 PM, David Malcolm <dmalcolm@redhat.com> wrote:
>
> On Mon, 2023-08-07 at 16:36 +0000, Li, Yicheng via Jit wrote:
>> Hi,
>>
>> I’m writing a paper on libgccjit.
>
> Excellent.  Would you be able to post a link to it when it's done?
>
>> But I cannot find the citation related to this.
>> Could you provide if there’s been a paper or citation?
>
> I don't know of an existing academic paper on libgccjit, or what the
> rules for citations are.
>
> FWIW, the earliest public reference to it I know of is my initial
> mailing list announcement here:
> https://gcc.gnu.org/legacy-ml/gcc-patches/2013-10/msg00228.html
>
> and the first presesntation I know of on it is the one I did at GNU
> Tools Cauldron 2014:
> https://dmalcolm.fedorapeople.org/presentations/cauldron-2014/jit/
> (slides)
> https://www.youtube.com/watch?v=XsaDtUkPu34&list=PLOGTP9W1DX5U53pPxtWdKkyiqe3GAn6Nd
> (video)
>
> The project's home page as such is this page on the GCC wiki:
> https://gcc.gnu.org/wiki/JIT
>
> Does this answer your questions?
>
> Thanks
> Dave
>


[-- Attachment #2: jit_pack_paper.pdf --]
[-- Type: application/pdf, Size: 958769 bytes --]

  reply	other threads:[~2023-08-07 17:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-07 16:36 Li, Yicheng
2023-08-07 17:20 ` David Malcolm
2023-08-07 17:23   ` Li, Yicheng [this message]
2023-08-08  8:30 ` Andrea Corallo

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=09823122-B031-4BAC-B9F0-471BD04A21C2@vols.utk.edu \
    --to=yli137@vols.utk.edu \
    --cc=dmalcolm@redhat.com \
    --cc=jit@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).