public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/105317] New: How to deal with this: internal compiler error: in process_init_constructor_array, at cp/typeck2.c:1308?
@ 2022-04-20  9:21 szy_mailbox at 126 dot com
  2022-04-20  9:50 ` [Bug c++/105317] " marxin at gcc dot gnu.org
                   ` (14 more replies)
  0 siblings, 15 replies; 16+ messages in thread
From: szy_mailbox at 126 dot com @ 2022-04-20  9:21 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105317

            Bug ID: 105317
           Summary: How to deal with this: internal compiler error: in
                    process_init_constructor_array, at cp/typeck2.c:1308?
           Product: gcc
           Version: 7.3.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: szy_mailbox at 126 dot com
  Target Milestone: ---

When i compile mysqlsrc with gcc7.3 on arm, it reports the following error:

[ 67%] Built target routertest_http_kdf_sha_crypt
Scanning dependencies of target routertest_http_http_uri
[ 67%] Building CXX object
unittest/gunit/xplugin/xcl/CMakeFiles/xclient_unit_tests.dir/xpriority_list_t.cc.o
/root/rpmbuild/BUILD/mysql-8.0.27/unittest/gunit/xplugin/xcl/xpriority_list_t.cc:
In member function ‘virtual void
xcl::test::Xcl_xpriority_list_tests_simple_operations_Test::TestBody()’:
/root/rpmbuild/BUILD/mysql-8.0.27/unittest/gunit/xplugin/xcl/xpriority_list_t.cc:167:57:
internal compiler error: in process_init_constructor_array, at
cp/typeck2.c:1308
   push_and_assert("Push_one_element", {"A"}, {F{"A", 1}});
                                                         ^
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://gcc.gnu.org/bugs/> for instructions.
make[2]: ***
[unittest/gunit/xplugin/xcl/CMakeFiles/xclient_unit_tests.dir/build.make:310:
unittest/gunit/xplugin/xcl/CMakeFiles/xclient_unit_tests.dir/xpriority_list_t.cc.o]
Error 1
make[1]: *** [CMakeFiles/Makefile2:25931:
unittest/gunit/xplugin/xcl/CMakeFiles/xclient_unit_tests.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....


gcc version is:

[root@abc]# gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/aarch64-linux-gnu/7.3.0/lto-wrapper
Target: aarch64-linux-gnu
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
--infodir=/usr/share/info --enable-shared --enable-threads=posix
--enable-checking=release --with-system-zlib --enable-__cxa_atexit
--disable-libunwind-exceptions --enable-gnu-unique-object
--enable-linker-build-id --with-linker-hash-style=gnu
--enable-languages=c,c++,objc,obj-c++,fortran,lto --enable-plugin
--enable-initfini-array --disable-libgcj
--with-isl=/home/abuild/rpmbuild/BUILD/gcc-7.3.0/obj-aarch64-linux-gnu/isl-install
--without-cloog --enable-gnu-indirect-function --build=aarch64-linux-gnu
--with-stage1-ldflags=' -Wl,-z,relro,-z,now' --with-boot-ldflags='
-Wl,-z,relro,-z,now' --with-multilib-list=lp64
Thread model: posix
gcc version 7.3.0 (GCC)

^ permalink raw reply	[flat|nested] 16+ messages in thread

* [Bug c++/105317] How to deal with this: internal compiler error: in process_init_constructor_array, at cp/typeck2.c:1308?
  2022-04-20  9:21 [Bug c++/105317] New: How to deal with this: internal compiler error: in process_init_constructor_array, at cp/typeck2.c:1308? szy_mailbox at 126 dot com
@ 2022-04-20  9:50 ` marxin at gcc dot gnu.org
  2022-04-20  9:58 ` szy_mailbox at 126 dot com
                   ` (13 subsequent siblings)
  14 siblings, 0 replies; 16+ messages in thread
From: marxin at gcc dot gnu.org @ 2022-04-20  9:50 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105317

Martin Liška <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |marxin at gcc dot gnu.org
   Last reconfirmed|                            |2022-04-20
             Status|UNCONFIRMED                 |WAITING
     Ever confirmed|0                           |1

--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Note, GCC 7.x is out of support. Can you please use something newer which is
GCC 9.x and later?

^ permalink raw reply	[flat|nested] 16+ messages in thread

* [Bug c++/105317] How to deal with this: internal compiler error: in process_init_constructor_array, at cp/typeck2.c:1308?
  2022-04-20  9:21 [Bug c++/105317] New: How to deal with this: internal compiler error: in process_init_constructor_array, at cp/typeck2.c:1308? szy_mailbox at 126 dot com
  2022-04-20  9:50 ` [Bug c++/105317] " marxin at gcc dot gnu.org
@ 2022-04-20  9:58 ` szy_mailbox at 126 dot com
  2022-04-20  9:59 ` szy_mailbox at 126 dot com
                   ` (12 subsequent siblings)
  14 siblings, 0 replies; 16+ messages in thread
From: szy_mailbox at 126 dot com @ 2022-04-20  9:58 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105317

--- Comment #2 from okay <szy_mailbox at 126 dot com> ---
Two consideration:

1) If i compile with high gcc version successfully, the code put on another
machine with low version libstdc++.so, the code may not run.

2) How to compile high gcc version source code on arm? Where can i find a
toturial? Is there any precompiled binary package?

^ permalink raw reply	[flat|nested] 16+ messages in thread

* [Bug c++/105317] How to deal with this: internal compiler error: in process_init_constructor_array, at cp/typeck2.c:1308?
  2022-04-20  9:21 [Bug c++/105317] New: How to deal with this: internal compiler error: in process_init_constructor_array, at cp/typeck2.c:1308? szy_mailbox at 126 dot com
  2022-04-20  9:50 ` [Bug c++/105317] " marxin at gcc dot gnu.org
  2022-04-20  9:58 ` szy_mailbox at 126 dot com
@ 2022-04-20  9:59 ` szy_mailbox at 126 dot com
  2022-04-20 10:04 ` marxin at gcc dot gnu.org
                   ` (11 subsequent siblings)
  14 siblings, 0 replies; 16+ messages in thread
From: szy_mailbox at 126 dot com @ 2022-04-20  9:59 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105317

--- Comment #3 from okay <szy_mailbox at 126 dot com> ---
Two consideration:

1) If i compile with high gcc version successfully, the code put on another
machine with low version libstdc++.so, the code may not run.

2) How to compile high gcc version source code on arm? Where can i find a
toturial? Is there any precompiled binary package?

^ permalink raw reply	[flat|nested] 16+ messages in thread

* [Bug c++/105317] How to deal with this: internal compiler error: in process_init_constructor_array, at cp/typeck2.c:1308?
  2022-04-20  9:21 [Bug c++/105317] New: How to deal with this: internal compiler error: in process_init_constructor_array, at cp/typeck2.c:1308? szy_mailbox at 126 dot com
                   ` (2 preceding siblings ...)
  2022-04-20  9:59 ` szy_mailbox at 126 dot com
@ 2022-04-20 10:04 ` marxin at gcc dot gnu.org
  2022-04-20 10:09 ` szy_mailbox at 126 dot com
                   ` (10 subsequent siblings)
  14 siblings, 0 replies; 16+ messages in thread
From: marxin at gcc dot gnu.org @ 2022-04-20 10:04 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105317

--- Comment #4 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to okay from comment #2)
> Two consideration:
> 
> 1) If i compile with high gcc version successfully, the code put on another
> machine with low version libstdc++.so, the code may not run.

You should also provide the corresponding libstdc++.so.

> 
> 2) How to compile high gcc version source code on arm? Where can i find a
> toturial? Is there any precompiled binary package?

What distribution do you use?

^ permalink raw reply	[flat|nested] 16+ messages in thread

* [Bug c++/105317] How to deal with this: internal compiler error: in process_init_constructor_array, at cp/typeck2.c:1308?
  2022-04-20  9:21 [Bug c++/105317] New: How to deal with this: internal compiler error: in process_init_constructor_array, at cp/typeck2.c:1308? szy_mailbox at 126 dot com
                   ` (3 preceding siblings ...)
  2022-04-20 10:04 ` marxin at gcc dot gnu.org
@ 2022-04-20 10:09 ` szy_mailbox at 126 dot com
  2022-04-20 10:10 ` marxin at gcc dot gnu.org
                   ` (9 subsequent siblings)
  14 siblings, 0 replies; 16+ messages in thread
From: szy_mailbox at 126 dot com @ 2022-04-20 10:09 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105317

--- Comment #5 from okay <szy_mailbox at 126 dot com> ---
The target is arm + euler.

^ permalink raw reply	[flat|nested] 16+ messages in thread

* [Bug c++/105317] How to deal with this: internal compiler error: in process_init_constructor_array, at cp/typeck2.c:1308?
  2022-04-20  9:21 [Bug c++/105317] New: How to deal with this: internal compiler error: in process_init_constructor_array, at cp/typeck2.c:1308? szy_mailbox at 126 dot com
                   ` (4 preceding siblings ...)
  2022-04-20 10:09 ` szy_mailbox at 126 dot com
@ 2022-04-20 10:10 ` marxin at gcc dot gnu.org
  2022-04-20 10:12 ` szy_mailbox at 126 dot com
                   ` (8 subsequent siblings)
  14 siblings, 0 replies; 16+ messages in thread
From: marxin at gcc dot gnu.org @ 2022-04-20 10:10 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105317

--- Comment #6 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to okay from comment #5)
> The target is arm + euler.

EulerOS or openEuler. How do you get the gcc7.3, is it a system compiler?

^ permalink raw reply	[flat|nested] 16+ messages in thread

* [Bug c++/105317] How to deal with this: internal compiler error: in process_init_constructor_array, at cp/typeck2.c:1308?
  2022-04-20  9:21 [Bug c++/105317] New: How to deal with this: internal compiler error: in process_init_constructor_array, at cp/typeck2.c:1308? szy_mailbox at 126 dot com
                   ` (5 preceding siblings ...)
  2022-04-20 10:10 ` marxin at gcc dot gnu.org
@ 2022-04-20 10:12 ` szy_mailbox at 126 dot com
  2022-04-20 10:13 ` marxin at gcc dot gnu.org
                   ` (7 subsequent siblings)
  14 siblings, 0 replies; 16+ messages in thread
From: szy_mailbox at 126 dot com @ 2022-04-20 10:12 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105317

--- Comment #7 from okay <szy_mailbox at 126 dot com> ---
using: yum install gCc-C++ libstdc++- devel

^ permalink raw reply	[flat|nested] 16+ messages in thread

* [Bug c++/105317] How to deal with this: internal compiler error: in process_init_constructor_array, at cp/typeck2.c:1308?
  2022-04-20  9:21 [Bug c++/105317] New: How to deal with this: internal compiler error: in process_init_constructor_array, at cp/typeck2.c:1308? szy_mailbox at 126 dot com
                   ` (6 preceding siblings ...)
  2022-04-20 10:12 ` szy_mailbox at 126 dot com
@ 2022-04-20 10:13 ` marxin at gcc dot gnu.org
  2022-04-20 10:16 ` szy_mailbox at 126 dot com
                   ` (6 subsequent siblings)
  14 siblings, 0 replies; 16+ messages in thread
From: marxin at gcc dot gnu.org @ 2022-04-20 10:13 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105317

--- Comment #8 from Martin Liška <marxin at gcc dot gnu.org> ---
EulerOS or openEuler?

what's your:
uname -a
?

^ permalink raw reply	[flat|nested] 16+ messages in thread

* [Bug c++/105317] How to deal with this: internal compiler error: in process_init_constructor_array, at cp/typeck2.c:1308?
  2022-04-20  9:21 [Bug c++/105317] New: How to deal with this: internal compiler error: in process_init_constructor_array, at cp/typeck2.c:1308? szy_mailbox at 126 dot com
                   ` (7 preceding siblings ...)
  2022-04-20 10:13 ` marxin at gcc dot gnu.org
@ 2022-04-20 10:16 ` szy_mailbox at 126 dot com
  2022-04-20 10:17 ` marxin at gcc dot gnu.org
                   ` (5 subsequent siblings)
  14 siblings, 0 replies; 16+ messages in thread
From: szy_mailbox at 126 dot com @ 2022-04-20 10:16 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105317

--- Comment #9 from okay <szy_mailbox at 126 dot com> ---
1 SMP Fri Jan 8 13:18:01 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux

^ permalink raw reply	[flat|nested] 16+ messages in thread

* [Bug c++/105317] How to deal with this: internal compiler error: in process_init_constructor_array, at cp/typeck2.c:1308?
  2022-04-20  9:21 [Bug c++/105317] New: How to deal with this: internal compiler error: in process_init_constructor_array, at cp/typeck2.c:1308? szy_mailbox at 126 dot com
                   ` (8 preceding siblings ...)
  2022-04-20 10:16 ` szy_mailbox at 126 dot com
@ 2022-04-20 10:17 ` marxin at gcc dot gnu.org
  2022-04-20 14:28 ` szy_mailbox at 126 dot com
                   ` (4 subsequent siblings)
  14 siblings, 0 replies; 16+ messages in thread
From: marxin at gcc dot gnu.org @ 2022-04-20 10:17 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105317

--- Comment #10 from Martin Liška <marxin at gcc dot gnu.org> ---
So you will need to investigate first which OS do you use and consider updating
it?

^ permalink raw reply	[flat|nested] 16+ messages in thread

* [Bug c++/105317] How to deal with this: internal compiler error: in process_init_constructor_array, at cp/typeck2.c:1308?
  2022-04-20  9:21 [Bug c++/105317] New: How to deal with this: internal compiler error: in process_init_constructor_array, at cp/typeck2.c:1308? szy_mailbox at 126 dot com
                   ` (9 preceding siblings ...)
  2022-04-20 10:17 ` marxin at gcc dot gnu.org
@ 2022-04-20 14:28 ` szy_mailbox at 126 dot com
  2022-04-20 14:33 ` jakub at gcc dot gnu.org
                   ` (3 subsequent siblings)
  14 siblings, 0 replies; 16+ messages in thread
From: szy_mailbox at 126 dot com @ 2022-04-20 14:28 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105317

--- Comment #11 from okay <szy_mailbox at 126 dot com> ---
I am not sure which one. Could you tell me both, thanks!

^ permalink raw reply	[flat|nested] 16+ messages in thread

* [Bug c++/105317] How to deal with this: internal compiler error: in process_init_constructor_array, at cp/typeck2.c:1308?
  2022-04-20  9:21 [Bug c++/105317] New: How to deal with this: internal compiler error: in process_init_constructor_array, at cp/typeck2.c:1308? szy_mailbox at 126 dot com
                   ` (10 preceding siblings ...)
  2022-04-20 14:28 ` szy_mailbox at 126 dot com
@ 2022-04-20 14:33 ` jakub at gcc dot gnu.org
  2022-04-20 14:42 ` szy_mailbox at 126 dot com
                   ` (2 subsequent siblings)
  14 siblings, 0 replies; 16+ messages in thread
From: jakub at gcc dot gnu.org @ 2022-04-20 14:33 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105317

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #12 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I don't think it really matters.  gcc 7 or 8 aren't supported anymore, there
won't be any further releases from those branches, so you either need to report
it to whomever provided you gcc if they still support that gcc by themselves,
or use a newer gcc, or find and backport a fix yourself, or find a workaround.
There is nothing we can do for you, unless the bug is still present in gcc 9 or
later.

^ permalink raw reply	[flat|nested] 16+ messages in thread

* [Bug c++/105317] How to deal with this: internal compiler error: in process_init_constructor_array, at cp/typeck2.c:1308?
  2022-04-20  9:21 [Bug c++/105317] New: How to deal with this: internal compiler error: in process_init_constructor_array, at cp/typeck2.c:1308? szy_mailbox at 126 dot com
                   ` (11 preceding siblings ...)
  2022-04-20 14:33 ` jakub at gcc dot gnu.org
@ 2022-04-20 14:42 ` szy_mailbox at 126 dot com
  2022-04-20 15:12 ` szy_mailbox at 126 dot com
  2022-04-20 15:33 ` szy_mailbox at 126 dot com
  14 siblings, 0 replies; 16+ messages in thread
From: szy_mailbox at 126 dot com @ 2022-04-20 14:42 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105317

--- Comment #13 from okay <szy_mailbox at 126 dot com> ---
Suppose using newer gcc, where can i download binary package or if compiling
from source gcc code, how to do?

^ permalink raw reply	[flat|nested] 16+ messages in thread

* [Bug c++/105317] How to deal with this: internal compiler error: in process_init_constructor_array, at cp/typeck2.c:1308?
  2022-04-20  9:21 [Bug c++/105317] New: How to deal with this: internal compiler error: in process_init_constructor_array, at cp/typeck2.c:1308? szy_mailbox at 126 dot com
                   ` (12 preceding siblings ...)
  2022-04-20 14:42 ` szy_mailbox at 126 dot com
@ 2022-04-20 15:12 ` szy_mailbox at 126 dot com
  2022-04-20 15:33 ` szy_mailbox at 126 dot com
  14 siblings, 0 replies; 16+ messages in thread
From: szy_mailbox at 126 dot com @ 2022-04-20 15:12 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105317

--- Comment #14 from okay <szy_mailbox at 126 dot com> ---
Btw, does the problem cause by lower gcc version 7.3? If using 7.5, can problem
be solved? The same mysql source code in x86 with gcc 7.5, it can be compiled
successfully.

^ permalink raw reply	[flat|nested] 16+ messages in thread

* [Bug c++/105317] How to deal with this: internal compiler error: in process_init_constructor_array, at cp/typeck2.c:1308?
  2022-04-20  9:21 [Bug c++/105317] New: How to deal with this: internal compiler error: in process_init_constructor_array, at cp/typeck2.c:1308? szy_mailbox at 126 dot com
                   ` (13 preceding siblings ...)
  2022-04-20 15:12 ` szy_mailbox at 126 dot com
@ 2022-04-20 15:33 ` szy_mailbox at 126 dot com
  14 siblings, 0 replies; 16+ messages in thread
From: szy_mailbox at 126 dot com @ 2022-04-20 15:33 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105317

okay <szy_mailbox at 126 dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |WONTFIX
             Status|WAITING                     |RESOLVED

^ permalink raw reply	[flat|nested] 16+ messages in thread

end of thread, other threads:[~2022-04-20 15:33 UTC | newest]

Thread overview: 16+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-04-20  9:21 [Bug c++/105317] New: How to deal with this: internal compiler error: in process_init_constructor_array, at cp/typeck2.c:1308? szy_mailbox at 126 dot com
2022-04-20  9:50 ` [Bug c++/105317] " marxin at gcc dot gnu.org
2022-04-20  9:58 ` szy_mailbox at 126 dot com
2022-04-20  9:59 ` szy_mailbox at 126 dot com
2022-04-20 10:04 ` marxin at gcc dot gnu.org
2022-04-20 10:09 ` szy_mailbox at 126 dot com
2022-04-20 10:10 ` marxin at gcc dot gnu.org
2022-04-20 10:12 ` szy_mailbox at 126 dot com
2022-04-20 10:13 ` marxin at gcc dot gnu.org
2022-04-20 10:16 ` szy_mailbox at 126 dot com
2022-04-20 10:17 ` marxin at gcc dot gnu.org
2022-04-20 14:28 ` szy_mailbox at 126 dot com
2022-04-20 14:33 ` jakub at gcc dot gnu.org
2022-04-20 14:42 ` szy_mailbox at 126 dot com
2022-04-20 15:12 ` szy_mailbox at 126 dot com
2022-04-20 15:33 ` szy_mailbox at 126 dot com

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).