public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "roland.illig at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/99304] New: typo in diagnostic: refernced
Date: Sat, 27 Feb 2021 12:54:20 +0000 [thread overview]
Message-ID: <bug-99304-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99304
Bug ID: 99304
Summary: typo in diagnostic: refernced
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
gcc/c-family/c-attribs.c says:
> "refernced symbol declared here"
That should be "referenced" instead.
A test to trigger this diagnostic is:
~~~c
/* { dg-do compile } */
/* { dg-options "-O2 -Wall" } */
void invalid_free(/* no prototype */); /* { dg-message "referenced" } */
void *invalid_malloc(void) __attribute__((
malloc(invalid_free) /* { dg-warning "must take a pointer" } */
));
~~~
A test to trigger the closely related diagnostic is:
~~~c
/* { dg-do compile } */
/* { dg-options "-O2 -Wall" } */
void invalid_free(int); /* { dg-message "referenced" } */
void *invalid_malloc(void) __attribute__((
malloc(invalid_free) /* { dg-warning "must take a pointer" } */
));
~~~
next reply other threads:[~2021-02-27 12:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-27 12:54 roland.illig at gmx dot de [this message]
2021-02-27 12:56 ` [Bug c/99304] " redi at gcc dot gnu.org
2021-02-27 12:57 ` [Bug c/99304] [11 Regression] " redi at gcc dot gnu.org
2021-02-27 14:50 ` jakub at gcc dot gnu.org
2021-02-28 10:13 ` cvs-commit at gcc dot gnu.org
2021-02-28 10:19 ` jakub at gcc dot gnu.org
2021-02-28 11:41 ` roland.illig at gmx dot de
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-99304-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: 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).