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] how-to-use-inline-assembly-language-in-c-code page is huge and should be split up
Date: Sat, 12 Nov 2022 00:20:28 +0000	[thread overview]
Message-ID: <bug-107653-4-mLSw6AkTjT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107653-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107653

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #1)
> I thought it went one layer deap but nope it is kinda of random.
> For an example:
> Not split up:
> https://gcc.gnu.org/onlinedocs/gccint/target-macros/register-classes.html
> 
> Splitted up:
> https://gcc.gnu.org/onlinedocs/gccint/target-macros/stack-layout-and-calling-
> conventions.html
> 
> Both are on the same level and both have similar amount of information on
> each section as far as I can tell.
> 
> Does anyone understand how it was decided to split it up vs not splitting up?

Sorry I copied the wrong one which was not split up.
I Mean
https://gcc.gnu.org/onlinedocs/gccint/target-macros/register-usage.html#

Also the left side bar has an arrow next to that one but it expands to nothing.

  parent reply	other threads:[~2022-11-12  0:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-11 21:22 [Bug c/107653] New: " pinskia at gcc dot gnu.org
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 [this message]
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-mLSw6AkTjT@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).