public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jdx at o2 dot pl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/109293] New: Missing memmem() prototype in fixincludes/fixfixes.c on Windows/MinGW-W64
Date: Mon, 27 Mar 2023 09:19:56 +0000 [thread overview]
Message-ID: <bug-109293-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109293
Bug ID: 109293
Summary: Missing memmem() prototype in fixincludes/fixfixes.c
on Windows/MinGW-W64
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Keywords: build
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: jdx at o2 dot pl
Target Milestone: ---
Host: x86_64-w64-mingw32
Created attachment 54763
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54763&action=edit
Proposed patch
gcc -c -g -O2 -W -Wall -Wwrite-strings -Wstrict-prototypes
-Wmissing-prototypes -Wold-style-definition -Wmissing-format-attribute
-Wno-overlength-strings -pedantic -Wno-long-long -DHAVE_CONFIG_H -I.
-I../../../gcc/fixincludes -I../include -I../../../gcc/fixincludes/../include
../../../gcc/fixincludes/fixfixes.c
../../../gcc/fixincludes/fixfixes.c: In function 'check_has_inc':
../../../gcc/fixincludes/fixfixes.c:490:12: warning: implicit declaration of
function 'memmem'; did you mean 'memset'? [-Wimplicit-function-declaration]
490 | for (p = memmem (begin, pos - begin, has_inc, has_inc_len);
| ^~~~~~
| memset
../../../gcc/fixincludes/fixfixes.c:490:10: warning: assignment to 'const char
*' from 'int' makes pointer from integer without a cast [-Wint-conversion]
490 | for (p = memmem (begin, pos - begin, has_inc, has_inc_len);
| ^
../../../gcc/fixincludes/fixfixes.c:492:10: warning: assignment to 'const char
*' from 'int' makes pointer from integer without a cast [-Wint-conversion]
492 | p = memmem (p, pos - p, has_inc, has_inc_len))
| ^
next reply other threads:[~2023-03-27 9:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 9:19 jdx at o2 dot pl [this message]
2023-03-27 15:42 ` [Bug other/109293] [12/13 Regression] " pinskia at gcc dot gnu.org
2023-03-27 16:02 ` xry111 at gcc dot gnu.org
2023-03-27 16:09 ` xry111 at gcc dot gnu.org
2023-03-27 16:13 ` pinskia at gcc dot gnu.org
2023-03-27 16:15 ` xry111 at gcc dot gnu.org
2023-03-27 16:19 ` pinskia at gcc dot gnu.org
2023-03-27 16:20 ` xry111 at gcc dot gnu.org
2023-03-28 7:26 ` cvs-commit at gcc dot gnu.org
2023-03-28 7:28 ` [Bug other/109293] [12 " xry111 at gcc dot gnu.org
2023-03-28 9:30 ` jdx at o2 dot pl
2023-03-28 10:01 ` cvs-commit at gcc dot gnu.org
2023-03-28 10:02 ` xry111 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-109293-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).