* [Bug bootstrap/98300] GCC 11 failed to build on Windows 10. I guess the new module completely breaks this.
2020-12-15 19:31 [Bug bootstrap/98300] New: GCC 11 failed to build on Windows 10. I guess the new module completely breaks this euloanty at live dot com
@ 2020-12-15 19:37 ` euloanty at live dot com
2020-12-15 19:41 ` euloanty at live dot com
` (12 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: euloanty at live dot com @ 2020-12-15 19:37 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98300
fdlbxtqi <euloanty at live dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target| |x86_64-msys2-mingw-w64,
| |windows 10
Host| |x86_64-msys2-mingw-w64,
| |windows 10
CC| |euloanty at live dot com
--- Comment #1 from fdlbxtqi <euloanty at live dot com> ---
The assumption of libcody of POSIX apis do not actually exist on windows.
Windows does not represent socket as fd.
There is no O_CLOEXEC on Windows. O_INHERIT can be a replacement.
no sys/mman.h on Windows
^ permalink raw reply [flat|nested] 15+ messages in thread
* [Bug bootstrap/98300] GCC 11 failed to build on Windows 10. I guess the new module completely breaks this.
2020-12-15 19:31 [Bug bootstrap/98300] New: GCC 11 failed to build on Windows 10. I guess the new module completely breaks this euloanty at live dot com
2020-12-15 19:37 ` [Bug bootstrap/98300] " euloanty at live dot com
@ 2020-12-15 19:41 ` euloanty at live dot com
2020-12-15 19:42 ` nathan at gcc dot gnu.org
` (11 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: euloanty at live dot com @ 2020-12-15 19:41 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98300
--- Comment #2 from fdlbxtqi <euloanty at live dot com> ---
Here was an older version (GCC11 20201204) that can be used for bootstrapping.
Please, thank you for fixing this issue ASAP.
https://bitbucket.org/ejsvifq_mabmip/mingw-gcc/src/master/
^ permalink raw reply [flat|nested] 15+ messages in thread
* [Bug bootstrap/98300] GCC 11 failed to build on Windows 10. I guess the new module completely breaks this.
2020-12-15 19:31 [Bug bootstrap/98300] New: GCC 11 failed to build on Windows 10. I guess the new module completely breaks this euloanty at live dot com
2020-12-15 19:37 ` [Bug bootstrap/98300] " euloanty at live dot com
2020-12-15 19:41 ` euloanty at live dot com
@ 2020-12-15 19:42 ` nathan at gcc dot gnu.org
2020-12-15 19:43 ` euloanty at live dot com
` (10 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: nathan at gcc dot gnu.org @ 2020-12-15 19:42 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98300
--- Comment #3 from Nathan Sidwell <nathan at gcc dot gnu.org> ---
Hm, I thought there was sufficient #ifing to prevent that ...
^ permalink raw reply [flat|nested] 15+ messages in thread
* [Bug bootstrap/98300] GCC 11 failed to build on Windows 10. I guess the new module completely breaks this.
2020-12-15 19:31 [Bug bootstrap/98300] New: GCC 11 failed to build on Windows 10. I guess the new module completely breaks this euloanty at live dot com
` (2 preceding siblings ...)
2020-12-15 19:42 ` nathan at gcc dot gnu.org
@ 2020-12-15 19:43 ` euloanty at live dot com
2020-12-15 19:48 ` euloanty at live dot com
` (9 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: euloanty at live dot com @ 2020-12-15 19:43 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98300
--- Comment #4 from fdlbxtqi <euloanty at live dot com> ---
(In reply to Nathan Sidwell from comment #3)
> Hm, I thought there was sufficient #ifing to prevent that ...
Try the compiler I build before to guard against this.
^ permalink raw reply [flat|nested] 15+ messages in thread
* [Bug bootstrap/98300] GCC 11 failed to build on Windows 10. I guess the new module completely breaks this.
2020-12-15 19:31 [Bug bootstrap/98300] New: GCC 11 failed to build on Windows 10. I guess the new module completely breaks this euloanty at live dot com
` (3 preceding siblings ...)
2020-12-15 19:43 ` euloanty at live dot com
@ 2020-12-15 19:48 ` euloanty at live dot com
2020-12-15 20:14 ` nathan at gcc dot gnu.org
` (8 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: euloanty at live dot com @ 2020-12-15 19:48 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98300
--- Comment #5 from fdlbxtqi <euloanty at live dot com> ---
(In reply to Nathan Sidwell from comment #3)
> Hm, I thought there was sufficient #ifing to prevent that ...
BTW. I tried the example you showed on the GCC module webpage on Linux. It
fails to compile. why?
cqwrteur@Home-Server:~/myhome/test_module$ vim hello.cc
cqwrteur@Home-Server:~/myhome/test_module$ vim a.cc
cqwrteur@Home-Server:~/myhome/test_module$ g++ -fmodules-ts hello.cc main.cc
-Ofast -std=c++20 -s
/usr/bin/ld: /tmp/ccQUwe74.o: in function `_GLOBAL__sub_I_main':
main.cc:(.text.startup+0x31): undefined reference to `_ZGIW5helloEv'
collect2: error: ld returned 1 exit status
My MinGW-w64 msys2 build script
Just run
makepkg-mingw
in the msys2 console and the compiler will get built.
https://bitbucket.org/ejsvifq_mabmip/mingw-gcc-mcf-gthread/src/master/
^ permalink raw reply [flat|nested] 15+ messages in thread
* [Bug bootstrap/98300] GCC 11 failed to build on Windows 10. I guess the new module completely breaks this.
2020-12-15 19:31 [Bug bootstrap/98300] New: GCC 11 failed to build on Windows 10. I guess the new module completely breaks this euloanty at live dot com
` (4 preceding siblings ...)
2020-12-15 19:48 ` euloanty at live dot com
@ 2020-12-15 20:14 ` nathan at gcc dot gnu.org
2020-12-15 20:17 ` euloanty at live dot com
` (7 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: nathan at gcc dot gnu.org @ 2020-12-15 20:14 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98300
--- Comment #6 from Nathan Sidwell <nathan at gcc dot gnu.org> ---
Created attachment 49769
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49769&action=edit
potential patch
Care to give this patch a try?
^ permalink raw reply [flat|nested] 15+ messages in thread
* [Bug bootstrap/98300] GCC 11 failed to build on Windows 10. I guess the new module completely breaks this.
2020-12-15 19:31 [Bug bootstrap/98300] New: GCC 11 failed to build on Windows 10. I guess the new module completely breaks this euloanty at live dot com
` (5 preceding siblings ...)
2020-12-15 20:14 ` nathan at gcc dot gnu.org
@ 2020-12-15 20:17 ` euloanty at live dot com
2020-12-15 20:34 ` euloanty at live dot com
` (6 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: euloanty at live dot com @ 2020-12-15 20:17 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98300
--- Comment #7 from fdlbxtqi <euloanty at live dot com> ---
(In reply to Nathan Sidwell from comment #6)
> Created attachment 49769 [details]
> potential patch
>
> Care to give this patch a try?
I will help you. no problem.
BTW. Welcome to join discord so I can show you details.
https://discord.gg/vMKhB9Q
^ permalink raw reply [flat|nested] 15+ messages in thread
* [Bug bootstrap/98300] GCC 11 failed to build on Windows 10. I guess the new module completely breaks this.
2020-12-15 19:31 [Bug bootstrap/98300] New: GCC 11 failed to build on Windows 10. I guess the new module completely breaks this euloanty at live dot com
` (6 preceding siblings ...)
2020-12-15 20:17 ` euloanty at live dot com
@ 2020-12-15 20:34 ` euloanty at live dot com
2020-12-15 23:02 ` euloanty at live dot com
` (5 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: euloanty at live dot com @ 2020-12-15 20:34 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98300
--- Comment #8 from fdlbxtqi <euloanty at live dot com> ---
(In reply to Nathan Sidwell from comment #6)
> Created attachment 49769 [details]
> potential patch
>
> Care to give this patch a try?
make[2]: Leaving directory
'/home/unlvs/mingw-gcc-mcf-gthread/src/build-x86_64-w64-mingw32/libcc1'
../../gcc-git/c++tools/server.cc: In function 'void crash_signal(int)':
../../gcc-git/c++tools/server.cc:216:32: error: 'strsignal' was not declared in
this scope; did you mean 'strsigno'?
216 | internal_error ("signal %s", strsignal (sig));
| ^~~~~~~~~
| strsigno
../../gcc-git/c++tools/server.cc:217:1: warning: 'noreturn' function does
return
217 | }
| ^
make[2]: *** [Makefile:72: server.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory
'/home/unlvs/mingw-gcc-mcf-gthread/src/build-x86_64-w64-mingw32/c++tools'
make[1]: *** [Makefile:10586: all-c++tools] Error 2
make[1]: *** Waiting for unfinished jobs....
configure: creating cache ./config.cache
checking build system type... x86_64-w64-mingw32
checking host system type... x86_64-w64-mingw32
checking for --enable-version-specific-runtime-libs... no
checking for a BSD-compatible install... /usr/bin/install -c
checking for gawk... gawk
checking for x86_64-w64-mingw32-ar... /mingw64/x86_64-w64-mingw32/bin/ar
checking for x86_64-w64-mingw32-lipo... lipo
checking for x86_64-w64-mingw32-nm...
/home/unlvs/mingw-gcc-mcf-gthread/src/build-x86_64-w64-mingw32/./gcc/nm
checking for x86_64-w64-mingw32-ranlib...
/mingw64/x86_64-w64-mingw32/bin/ranlib
checking for x86_64-w64-mingw32-strip... /mingw64/x86_64-w64-mingw32/bin/strip
checking whether ln -s works... no, using cp -pR
checking for x86_64-w64-mingw32-gcc...
/home/unlvs/mingw-gcc-mcf-gthread/src/build-x86_64-w64-mingw32/./gcc/xgcc
-B/home/unlvs/mingw-gcc-mcf-gthread/src/build-x86_64-w64-mingw32/./gcc/
-L/mingw64/x86_64-w64-mingw32/lib -L/mingw64/lib -isystem
/mingw64/x86_64-w64-mingw32/include -isystem /mingw64/include
-B/mingw64/x86_64-w64-mingw32/bin/ -B/mingw64/x86_64-w64-mingw32/lib/ -isystem
/mingw64/x86_64-w64-mingw32/include -isystem
/mingw64/x86_64-w64-mingw32/sys-include
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether
/home/unlvs/mingw-gcc-mcf-gthread/src/build-x86_64-w64-mingw32/./gcc/xgcc
-B/home/unlvs/mingw-gcc-mcf-gthread/src/build-x86_64-w64-mingw32/./gcc/
-L/mingw64/x86_64-w64-mingw32/lib -L/mingw64/lib -isystem
/mingw64/x86_64-w64-mingw32/include -isystem /mingw64/include
-B/mingw64/x86_64-w64-mingw32/bin/ -B/mingw64/x86_64-w64-mingw32/lib/ -isystem
/mingw64/x86_64-w64-mingw32/include -isystem
/mingw64/x86_64-w64-mingw32/sys-include accepts -g... yes
checking for
/home/unlvs/mingw-gcc-mcf-gthread/src/build-x86_64-w64-mingw32/./gcc/xgcc
-B/home/unlvs/mingw-gcc-mcf-gthread/src/build-x86_64-w64-mingw32/./gcc/
-L/mingw64/x86_64-w64-mingw32/lib -L/mingw64/lib -isystem
/mingw64/x86_64-w64-mingw32/include -isystem /mingw64/include
-B/mingw64/x86_64-w64-mingw32/bin/ -B/mingw64/x86_64-w64-mingw32/lib/ -isystem
/mingw64/x86_64-w64-mingw32/include -isystem
/mingw64/x86_64-w64-mingw32/sys-include option to accept ISO C89... none
needed
checking how to run the C preprocessor...
/home/unlvs/mingw-gcc-mcf-gthread/src/build-x86_64-w64-mingw32/./gcc/xgcc
-B/home/unlvs/mingw-gcc-mcf-gthread/src/build-x86_64-w64-mingw32/./gcc/
-L/mingw64/x86_64-w64-mingw32/lib -L/mingw64/lib -isystem
/mingw64/x86_64-w64-mingw32/include -isystem /mingw64/include
-B/mingw64/x86_64-w64-mingw32/bin/ -B/mingw64/x86_64-w64-mingw32/lib/ -isystem
/mingw64/x86_64-w64-mingw32/include -isystem
/mingw64/x86_64-w64-mingw32/sys-include -E
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... 64
checking size of double... 8
checking size of long double... 16
checking for inttypes.h... yes
checking for stdint.h... yes
checking for stdlib.h... yes
checking for ftw.h... yes
checking for unistd.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for string.h... yes
checking for strings.h... yes
checking for memory.h... yes
checking for sys/auxv.h... no
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ANSI C header files... yes
checking whether decimal floating point is supported... yes
checking whether fixed-point is supported... no
checking whether the compiler is configured for setjmp/longjmp exceptions... no
checking for CET support... no
checking if the linker
(/home/unlvs/mingw-gcc-mcf-gthread/src/build-x86_64-w64-mingw32/./gcc/collect-ld)
is GNU ld... yes
checking for thread model used by GCC... mcf
checking whether assembler supports CFI directives... yes
checking for target glibc version... 0.0
checking for __attribute__((visibility("hidden")))... no
checking for .cfi_sections .debug_frame... yes
checking whether the target assembler supports thread-local storage... yes
checking whether the thread-local storage support is from emutls... yes
checking if the assembler supports AVX... yes
checking for init priority support... yes
configure: updating cache ./config.cache
configure: creating ./config.status
config.status: creating Makefile
config.status: creating auto-target.h
config.status: executing default commands
make[1]: Leaving directory
'/home/unlvs/mingw-gcc-mcf-gthread/src/build-x86_64-w64-mingw32'
make: *** [Makefile:973: all] Error 2
==> ERROR: A failure occurred in build().
Aborting...
New bug. No strsignal.
^ permalink raw reply [flat|nested] 15+ messages in thread
* [Bug bootstrap/98300] GCC 11 failed to build on Windows 10. I guess the new module completely breaks this.
2020-12-15 19:31 [Bug bootstrap/98300] New: GCC 11 failed to build on Windows 10. I guess the new module completely breaks this euloanty at live dot com
` (7 preceding siblings ...)
2020-12-15 20:34 ` euloanty at live dot com
@ 2020-12-15 23:02 ` euloanty at live dot com
2020-12-16 13:12 ` redi at gcc dot gnu.org
` (4 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: euloanty at live dot com @ 2020-12-15 23:02 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98300
--- Comment #9 from fdlbxtqi <euloanty at live dot com> ---
(In reply to Nathan Sidwell from comment #6)
> Created attachment 49769 [details]
> potential patch
>
> Care to give this patch a try?
hello??
^ permalink raw reply [flat|nested] 15+ messages in thread
* [Bug bootstrap/98300] GCC 11 failed to build on Windows 10. I guess the new module completely breaks this.
2020-12-15 19:31 [Bug bootstrap/98300] New: GCC 11 failed to build on Windows 10. I guess the new module completely breaks this euloanty at live dot com
` (8 preceding siblings ...)
2020-12-15 23:02 ` euloanty at live dot com
@ 2020-12-16 13:12 ` redi at gcc dot gnu.org
2020-12-16 21:50 ` nathan at gcc dot gnu.org
` (3 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: redi at gcc dot gnu.org @ 2020-12-16 13:12 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98300
--- Comment #10 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Be patient, people have to sleep sometimes.
And please stop CCing me on everything, this is nothing to do with me and I
can't do anything about it.
^ permalink raw reply [flat|nested] 15+ messages in thread
* [Bug bootstrap/98300] GCC 11 failed to build on Windows 10. I guess the new module completely breaks this.
2020-12-15 19:31 [Bug bootstrap/98300] New: GCC 11 failed to build on Windows 10. I guess the new module completely breaks this euloanty at live dot com
` (9 preceding siblings ...)
2020-12-16 13:12 ` redi at gcc dot gnu.org
@ 2020-12-16 21:50 ` nathan at gcc dot gnu.org
2020-12-17 14:01 ` cvs-commit at gcc dot gnu.org
` (2 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: nathan at gcc dot gnu.org @ 2020-12-16 21:50 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98300
Nathan Sidwell <nathan at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |nathan at gcc dot gnu.org
Ever confirmed|0 |1
Last reconfirmed| |2020-12-16
^ permalink raw reply [flat|nested] 15+ messages in thread
* [Bug bootstrap/98300] GCC 11 failed to build on Windows 10. I guess the new module completely breaks this.
2020-12-15 19:31 [Bug bootstrap/98300] New: GCC 11 failed to build on Windows 10. I guess the new module completely breaks this euloanty at live dot com
` (10 preceding siblings ...)
2020-12-16 21:50 ` nathan at gcc dot gnu.org
@ 2020-12-17 14:01 ` cvs-commit at gcc dot gnu.org
2021-01-04 14:04 ` nathan at gcc dot gnu.org
2021-01-04 15:23 ` rguenth at gcc dot gnu.org
13 siblings, 0 replies; 15+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2020-12-17 14:01 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98300
--- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Nathan Sidwell <nathan@gcc.gnu.org>:
https://gcc.gnu.org/g:096164229a4c2d1efab9f259f50be1bdcdfc8abd
commit r11-6225-g096164229a4c2d1efab9f259f50be1bdcdfc8abd
Author: Nathan Sidwell <nathan@acm.org>
Date: Thu Dec 17 05:57:13 2020 -0800
bootstrap: Fix some windows issues [PR 98300]
When breaking out the sample server from the gcc/cp directory, it lost
its check for mmap, and the sample resolver just assumed it was there.
Fixed thusly. The non-mapping paths in module.cc weren't (recently)
excercised, and led to a signedness warning. Finally I'd missed
c++tools's config.h.in in the gcc_update script. There I took the
opportunity of adding a 'tools' segment of the dependency lists.
PR bootstrap/98300
contrib/
* gcc_update: Add c++tools/config.h.in.
c++tools/
* configure.ac: Check for sys/mman.h.
* resolver.cc: Don't assume mmap, O_CLOEXEC are available. Use
xmalloc.
* config.h.in: Regenerated.
* configure: Regenerated.
gcc/cp/
* module.cc: Fix ::read, ::write result signedness comparisons.
^ permalink raw reply [flat|nested] 15+ messages in thread
* [Bug bootstrap/98300] GCC 11 failed to build on Windows 10. I guess the new module completely breaks this.
2020-12-15 19:31 [Bug bootstrap/98300] New: GCC 11 failed to build on Windows 10. I guess the new module completely breaks this euloanty at live dot com
` (11 preceding siblings ...)
2020-12-17 14:01 ` cvs-commit at gcc dot gnu.org
@ 2021-01-04 14:04 ` nathan at gcc dot gnu.org
2021-01-04 15:23 ` rguenth at gcc dot gnu.org
13 siblings, 0 replies; 15+ messages in thread
From: nathan at gcc dot gnu.org @ 2021-01-04 14:04 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98300
Nathan Sidwell <nathan at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |WAITING
^ permalink raw reply [flat|nested] 15+ messages in thread
* [Bug bootstrap/98300] GCC 11 failed to build on Windows 10. I guess the new module completely breaks this.
2020-12-15 19:31 [Bug bootstrap/98300] New: GCC 11 failed to build on Windows 10. I guess the new module completely breaks this euloanty at live dot com
` (12 preceding siblings ...)
2021-01-04 14:04 ` nathan at gcc dot gnu.org
@ 2021-01-04 15:23 ` rguenth at gcc dot gnu.org
13 siblings, 0 replies; 15+ messages in thread
From: rguenth at gcc dot gnu.org @ 2021-01-04 15:23 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98300
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |FIXED
--- Comment #12 from Richard Biener <rguenth at gcc dot gnu.org> ---
Fixed (please re-open if not).
^ permalink raw reply [flat|nested] 15+ messages in thread