* [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