[Bug middle-end/107656] post sphinx conversion, can't tell between a target macro or a target hook
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107656 Martin Liška changed: What|Removed |Added Resolution|--- |WONTFIX Status|NEW |RESOLVED --- Comment #4 from Martin Liška --- The Sphinx documentation has been reverted: https://gcc.gnu.org/pipermail/gcc/2022-November/239983.html Thus, I'm closing this as won't fix.
[Bug middle-end/107656] post sphinx conversion, can't tell between a target macro or a target hook
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107656 --- Comment #3 from Andrew Pinski --- (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).
[Bug middle-end/107656] post sphinx conversion, can't tell between a target macro or a target hook
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107656 Martin Liška changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW CC||marxin at gcc dot gnu.org Last reconfirmed||2022-11-13 --- Comment #2 from Martin Liška --- Yes, it's a small drawback. One can distinguish macros by missing return type, but I can imagine adding a .. note:: Target macro for such macros that have arguments. These w/o arguments are hopefully distinguishable from hooks.
[Bug middle-end/107656] post sphinx conversion, can't tell between a target macro or a target hook
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107656 --- Comment #1 from Andrew Pinski --- .. c:macro:: PROMOTE_MODE (m, unsignedp, type) .. function:: enum flt_eval_method TARGET_C_EXCESS_PRECISION (enum excess_precision_type type) It is really hard to tell the difference in the generated page though; especially since target macros and hooks can sometimes take arguments.
