From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 31F6F3858D35; Fri, 11 Nov 2022 21:22:42 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 31F6F3858D35
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1668201762;
	bh=S/HPg2kyOKLCLEg75cnOl4x4hmtQZzCxVkTsK5Cwuh0=;
	h=From:To:Subject:Date:From;
	b=b5yW1Xc7FbOPvoXtN6GZ911/wh+TVafvXcDmJtDFLK3dGv8d8fQinVIm+XDQQE4ig
	 FKW3/e5XXAbBzWj6jOZcRQmrMjxn2djsXX6EXhIiW1v9ChCgGk5JLDshqFxsrRYFHq
	 5IBrt+lou+a7c8a/sMSdxmybS0hWDMoHkkwAaUq0=
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
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 13.0
X-Bugzilla-Keywords: documentation, inline-asm
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status
 keywords bug_severity priority component assigned_to reporter
 target_milestone
Message-ID: <bug-107653-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

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

            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=20

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#Mach=
ine-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.=