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] New: post sphinx conversion, can't tell between a target macro or a target hook Date: Fri, 11 Nov 2022 23:27:25 +0000 [thread overview] Message-ID: <bug-107656-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107656 Bug ID: 107656 Summary: post sphinx conversion, can't tell between a target macro or a target hook Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: documentation Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: pinskia at gcc dot gnu.org Blocks: 107655 Target Milestone: --- https://gcc.gnu.org/onlinedocs/gccint/target-macros/storage-layout.html https://gcc.gnu.org/onlinedocs/gcc-12.2.0/gccint/Storage-Layout.html#Storage-Layout For an example PROMOTE_MODE, in the texinfo version, it has: Macro: PROMOTE_MODE (m, unsignedp, type) while for TARGET_C_EXCESS_PRECISION: Target Hook: enum flt_eval_method TARGET_C_EXCESS_PRECISION (enum excess_precision_type type) But in the sphinx version, it does not list if it was a macro or a hook. Which makes these confusing of what each is. Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107655 [Bug 107655] [meta-bug] tracker bug for issues encountered in the texinfo-to-sphinx migration
next reply other threads:[~2022-11-11 23:27 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-11 23:27 pinskia at gcc dot gnu.org [this message] 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 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@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).