From: LIU Hao <lh_mouse@126.com>
To: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Cc: jason@redhat.com, jchapman@lock3software.com
Subject: GCC 13 bootstrap failure on i686-w64-mingw32
Date: Sun, 20 Nov 2022 20:35:37 +0800 [thread overview]
Message-ID: <8d31dc28-47ce-a47a-254a-6f1c809b19b1@126.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1558 bytes --]
This is caused by 2efb237ffc68ec9bb17982434f5941bfa14f8b50, which has references to `strchrnul`,
which does not exist on i686w-64-mingw32:
```
g++ -std=c++11 -fno-PIE -c -DIN_GCC_FRONTEND -g -D__USE_MINGW_ACCESS -DIN_GCC
-fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings
-Wcast-qual -Wno-format -Wmissing-format-attribute -Woverloaded-virtual -pedantic -Wno-long-long
-Wno-variadic-macros -Wno-overlength-strings -DHAVE_CONFIG_H -I. -Icp -I../../gcc/gcc
-I../../gcc/gcc/cp -I../../gcc/gcc/../include -I../../gcc/gcc/../libcpp/include
-I../../gcc/gcc/../libcody -I/mingw32/include -I/mingw32/include -I/mingw32/include
-I../../gcc/gcc/../libdecnumber -I../../gcc/gcc/../libdecnumber/bid -I../libdecnumber
-I../../gcc/gcc/../libbacktrace -I/mingw32/include -D__USE_MINGW_ANSI_STDIO=1 -I/mingw32/include -o
cp/error.o -MT cp/error.o -MMD -MP -MF cp/.deps/error.TPo ../../gcc/gcc/cp/error.cc
../../gcc/gcc/cp/contracts.cc: In function 'bool role_name_equal(const char*, const char*)':
../../gcc/gcc/cp/contracts.cc:213:21: error: 'strchrnul' was not declared in this scope; did you
mean 'strchr'?
213 | size_t role_len = strchrnul (role, ':') - role;
| ^~~~~~~~~
| strchr
make[3]: *** [Makefile:1146: cp/contracts.o] Error 1
make[3]: *** Waiting for unfinished jobs....
```
Proposed solution:
```
size_t role_len = strcspn (role, ":");
```
--
Best regards,
LIU Hao
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next reply other threads:[~2022-11-20 12:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-20 12:35 LIU Hao [this message]
2022-11-20 19:17 ` Jonathan Wakely
2022-11-21 13:55 ` David Edelsohn
2022-11-21 13:59 ` Jonathan Wakely
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=8d31dc28-47ce-a47a-254a-6f1c809b19b1@126.com \
--to=lh_mouse@126.com \
--cc=gcc@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=jchapman@lock3software.com \
/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).