public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/107656] post sphinx conversion, can't tell between a target macro or a target hook
Date: Sun, 13 Nov 2022 19:43:02 +0000 [thread overview]
Message-ID: <bug-107656-4-tXjWCrGGme@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107656-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107656
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Martin Liška from comment #2)
> Yes, it's a small drawback.
IT IS NOT A SMALL DRAWBACK. It is a huge one really. Especially when a new
developer is trying to write a backend, they can't figure out if it was a
target hook or a target macro one is. The return type is only part is not
described anywhere to say it is the difference either. Epsecially when reading
each of these sections seperately.
I only noticed this because I am going to try to improve the documentation on
some of these and this caught my eye and made me even more confused (I looked
at the new documentation first and I was wait isn't one a target hook and then
I had to go look at the previous texinfo documentation to see that was true).
next prev parent reply other threads:[~2022-11-13 19:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 23:27 [Bug middle-end/107656] New: " pinskia at gcc dot gnu.org
2022-11-11 23:30 ` [Bug middle-end/107656] " pinskia at gcc dot gnu.org
2022-11-13 19:30 ` marxin at gcc dot gnu.org
2022-11-13 19:43 ` pinskia at gcc dot gnu.org [this message]
2022-11-14 8:43 ` marxin 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-107656-4-tXjWCrGGme@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).