public inbox for jit@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Malcolm <dmalcolm@redhat.com>
To: Eric Gallager <egall@gwmail.gwu.edu>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
	jit@gcc.gnu.org, Petter Tomner <tomner@kth.se>
Subject: Re: [committed] jit: further doc fixes
Date: Fri, 01 Apr 2022 18:55:42 -0400	[thread overview]
Message-ID: <73f654abe1bc29ad41b00f36f9cefb83a71d0aee.camel@redhat.com> (raw)
In-Reply-To: <CAMfHzOtzJ9KmppUo+jtt+ROmK70wYH5OqHfQXx1s6xzVAgY+pQ@mail.gmail.com>

On Fri, 2022-04-01 at 12:26 -0400, Eric Gallager wrote:
> On Fri, Apr 1, 2022 at 9:28 AM David Malcolm via Gcc-patches
> <gcc-patches@gcc.gnu.org> wrote:
> > 
> > Further jit doc fixes, which fix links to
> > gcc_jit_function_type_get_param_type and gcc_jit_struct_get_field.
> > 
> > I also regenerated libgccjit.texi (not included in the diff below).
> > 
> > Tested with "make html" and with a bootstrap.
> 
>  Could you test with `make pdf` and `make dvi` too, to see if this
> fixes 102824?
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102824

FWIW it doesn't fix that, but I've added some notes to that bug with a
possible fix.

Dave





  reply	other threads:[~2022-04-01 22:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-19 15:34 [PATCH] JIT: Update docs v2 Petter Tomner
2022-04-01 13:24 ` David Malcolm
2022-04-01 13:27   ` [committed] jit: further doc fixes David Malcolm
2022-04-01 16:26     ` Eric Gallager
2022-04-01 22:55       ` David Malcolm [this message]
2022-04-06 20:29       ` [committed] jit: fix location of .png files for "make jit.pdf" [PR102824] David Malcolm

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=73f654abe1bc29ad41b00f36f9cefb83a71d0aee.camel@redhat.com \
    --to=dmalcolm@redhat.com \
    --cc=egall@gwmail.gwu.edu \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jit@gcc.gnu.org \
    --cc=tomner@kth.se \
    /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).