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 c/107653] New: how-to-use-inline-assembly-language-in-c-code page is huge and should be split up Date: Fri, 11 Nov 2022 21:22:41 +0000 [thread overview] Message-ID: <bug-107653-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107653 Bug ID: 107653 Summary: how-to-use-inline-assembly-language-in-c-code page is huge and should be split up Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: documentation, inline-asm Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: pinskia at gcc dot gnu.org Target Milestone: --- https://gcc.gnu.org/onlinedocs/gcc/extensions-to-the-c-language-family/how-to-use-inline-assembly-language-in-c-code.html really needs to split up into many different pages. Compared to https://gcc.gnu.org/onlinedocs/gcc-12.2.0/gcc/Using-Assembly-Language-with-C.html#Using-Assembly-Language-with-C Having smaller pages is very useful, especially when you are going to just look at target constraints (which was a huge page even for texinfo generated documents): https://gcc.gnu.org/onlinedocs/gcc-12.2.0/gcc/Machine-Constraints.html#Machine-Constraints having all information on inline-asm on one page makes it hard to figure out things even with the right side bar. The seperate pages of the texinfo generated files makes it easier to navigate especially to the specific topic you want to navigate to. Having a TOC page for each section is very very useful; the side bar only goes so far of describing things. Note I have not double checked to make sure that the internals document and the user manual are shared or not here plus disabling of some of the constraints for the user manual either.
next reply other threads:[~2022-11-11 21:22 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-11 21:22 pinskia at gcc dot gnu.org [this message] 2022-11-12 0:17 ` [Bug c/107653] " pinskia at gcc dot gnu.org 2022-11-12 0:20 ` pinskia at gcc dot gnu.org 2022-11-13 19:25 ` marxin 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-107653-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).