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/107942] [10/11/12/13 Regression] Documentation of the volatile style for noreturn is gone and const style for const attribute is gone
Date: Thu, 01 Dec 2022 00:14:05 +0000 [thread overview]
Message-ID: <bug-107942-4-nZX0q52Xiy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107942-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107942
--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #5)
> Oh it is still part of the keyword index too:
> https://gcc.gnu.org/onlinedocs/gcc/Keyword-Index.html#Keyword-Index
>
> Which links to:
> https://gcc.gnu.org/onlinedocs/gcc/Function-Attributes.html#index-volatile-
> applied-to-function
Likewise for const:
https://gcc.gnu.org/onlinedocs/gcc/Function-Attributes.html#index-const-applied-to-function
next prev parent reply other threads:[~2022-12-01 0:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 23:49 [Bug c/107942] New: [10/11/12/13 Regression] Documentation of the volatile style for noreturn " pinskia at gcc dot gnu.org
2022-11-30 23:51 ` [Bug c/107942] " pinskia at gcc dot gnu.org
2022-11-30 23:58 ` [Bug c/107942] [10/11/12/13 Regression] Documentation of the volatile style for noreturn is gone and const style for const attribute " pinskia at gcc dot gnu.org
2022-12-01 0:07 ` pinskia at gcc dot gnu.org
2022-12-01 0:09 ` pinskia at gcc dot gnu.org
2022-12-01 0:13 ` pinskia at gcc dot gnu.org
2022-12-01 0:14 ` pinskia at gcc dot gnu.org [this message]
2022-12-21 13:33 ` rguenth at gcc dot gnu.org
2023-07-07 10:44 ` [Bug c/107942] [11/12/13/14 " rguenth at gcc dot gnu.org
2024-01-18 18:41 ` cvs-commit at gcc dot gnu.org
2024-01-18 18:43 ` sandra 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-107942-4-nZX0q52Xiy@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).