public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/99295] [11 Regression] documentation on __attribute__((malloc)) is wrong
Date: Sat, 27 Feb 2021 13:04:31 +0000 [thread overview]
Message-ID: <bug-99295-4-qji18PrHac@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99295-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99295
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |documentation
Known to work| |10.2.1
Last reconfirmed| |2021-02-27
Status|UNCONFIRMED |NEW
CC| |msebor at gcc dot gnu.org
Summary|documentation on |[11 Regression]
|__attribute__((malloc)) is |documentation on
|wrong |__attribute__((malloc)) is
| |wrong
Ever confirmed|0 |1
Target Milestone|--- |11.0
Known to fail| |11.0
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
This changed in dce6c58db87ebf7f4477bd3126228e73e4eeee97
next prev parent reply other threads:[~2021-02-27 13:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-26 23:25 [Bug c/99295] New: " roland.illig at gmx dot de
2021-02-26 23:27 ` [Bug c/99295] " roland.illig at gmx dot de
2021-02-27 13:04 ` redi at gcc dot gnu.org [this message]
2021-03-01 9:05 ` [Bug c/99295] [11 Regression] " rguenth at gcc dot gnu.org
2021-03-01 17:46 ` [Bug c/99295] [9/10/11 " msebor at gcc dot gnu.org
2021-03-02 18:21 ` cvs-commit at gcc dot gnu.org
2021-03-02 18:22 ` [Bug c/99295] [9/10 " msebor at gcc dot gnu.org
2021-03-06 22:42 ` roland.illig at gmx dot de
2021-04-27 11:40 ` jakub at gcc dot gnu.org
2021-07-28 7:06 ` rguenth at gcc dot gnu.org
2021-07-28 17:45 ` cvs-commit at gcc dot gnu.org
2021-07-28 17:46 ` [Bug c/99295] [9 " msebor at gcc dot gnu.org
2022-03-17 19:41 ` msebor 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-99295-4-qji18PrHac@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).