* [Bug target/109629] internal compiler error: in final_scan_insn_1, at final.c:3078 6480 | }
2023-04-26 1:15 [Bug c++/109629] New: internal compiler error: in final_scan_insn_1, at final.c:3078 6480 | } linus.zhu at mavenir dot com
@ 2023-04-26 1:20 ` pinskia at gcc dot gnu.org
2023-04-26 1:22 ` pinskia at gcc dot gnu.org
` (17 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: pinskia at gcc dot gnu.org @ 2023-04-26 1:20 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109629
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ice-on-valid-code
Component|c++ |target
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Note this:
See <http://bugzilla.redhat.com/bugzilla> for instructions.
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug target/109629] internal compiler error: in final_scan_insn_1, at final.c:3078 6480 | }
2023-04-26 1:15 [Bug c++/109629] New: internal compiler error: in final_scan_insn_1, at final.c:3078 6480 | } linus.zhu at mavenir dot com
2023-04-26 1:20 ` [Bug target/109629] " pinskia at gcc dot gnu.org
@ 2023-04-26 1:22 ` pinskia at gcc dot gnu.org
2023-04-26 1:26 ` linus.zhu at mavenir dot com
` (16 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: pinskia at gcc dot gnu.org @ 2023-04-26 1:22 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109629
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2023-04-26
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Also note:
Preprocessed source stored into /tmp/ccdNSTWA.out file, please attach this to
your bugreport.
You might need to compress it.
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug target/109629] internal compiler error: in final_scan_insn_1, at final.c:3078 6480 | }
2023-04-26 1:15 [Bug c++/109629] New: internal compiler error: in final_scan_insn_1, at final.c:3078 6480 | } linus.zhu at mavenir dot com
2023-04-26 1:20 ` [Bug target/109629] " pinskia at gcc dot gnu.org
2023-04-26 1:22 ` pinskia at gcc dot gnu.org
@ 2023-04-26 1:26 ` linus.zhu at mavenir dot com
2023-04-26 1:27 ` linus.zhu at mavenir dot com
` (15 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: linus.zhu at mavenir dot com @ 2023-04-26 1:26 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109629
--- Comment #3 from Linus <linus.zhu at mavenir dot com> ---
Created attachment 54921
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54921&action=edit
ccdNSTWA.out.1
ccdNSTWA.out.1
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug target/109629] internal compiler error: in final_scan_insn_1, at final.c:3078 6480 | }
2023-04-26 1:15 [Bug c++/109629] New: internal compiler error: in final_scan_insn_1, at final.c:3078 6480 | } linus.zhu at mavenir dot com
` (2 preceding siblings ...)
2023-04-26 1:26 ` linus.zhu at mavenir dot com
@ 2023-04-26 1:27 ` linus.zhu at mavenir dot com
2023-04-26 1:34 ` pinskia at gcc dot gnu.org
` (14 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: linus.zhu at mavenir dot com @ 2023-04-26 1:27 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109629
--- Comment #4 from Linus <linus.zhu at mavenir dot com> ---
due to 1M-attachment limit, I'll raise another bug and attach ccdNSTWA.out.2
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug target/109629] internal compiler error: in final_scan_insn_1, at final.c:3078 6480 | }
2023-04-26 1:15 [Bug c++/109629] New: internal compiler error: in final_scan_insn_1, at final.c:3078 6480 | } linus.zhu at mavenir dot com
` (3 preceding siblings ...)
2023-04-26 1:27 ` linus.zhu at mavenir dot com
@ 2023-04-26 1:34 ` pinskia at gcc dot gnu.org
2023-04-26 1:35 ` pinskia at gcc dot gnu.org
` (13 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: pinskia at gcc dot gnu.org @ 2023-04-26 1:34 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109629
--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
/* If we have a length attribute, this instruction should have
been split in shorten_branches, to ensure that we would have
valid length info for the splitees. */
gcc_assert (!HAVE_ATTR_length);
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug target/109629] internal compiler error: in final_scan_insn_1, at final.c:3078 6480 | }
2023-04-26 1:15 [Bug c++/109629] New: internal compiler error: in final_scan_insn_1, at final.c:3078 6480 | } linus.zhu at mavenir dot com
` (4 preceding siblings ...)
2023-04-26 1:34 ` pinskia at gcc dot gnu.org
@ 2023-04-26 1:35 ` pinskia at gcc dot gnu.org
2023-04-26 1:36 ` pinskia at gcc dot gnu.org
` (12 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: pinskia at gcc dot gnu.org @ 2023-04-26 1:35 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109629
--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
*** Bug 109630 has been marked as a duplicate of this bug. ***
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug target/109629] internal compiler error: in final_scan_insn_1, at final.c:3078 6480 | }
2023-04-26 1:15 [Bug c++/109629] New: internal compiler error: in final_scan_insn_1, at final.c:3078 6480 | } linus.zhu at mavenir dot com
` (5 preceding siblings ...)
2023-04-26 1:35 ` pinskia at gcc dot gnu.org
@ 2023-04-26 1:36 ` pinskia at gcc dot gnu.org
2023-04-26 1:54 ` linus.zhu at mavenir dot com
` (11 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: pinskia at gcc dot gnu.org @ 2023-04-26 1:36 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109629
--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Linus from comment #4)
> due to 1M-attachment limit, I'll raise another bug and attach ccdNSTWA.out.2
The limit is just per-attachment, not per bug.
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug target/109629] internal compiler error: in final_scan_insn_1, at final.c:3078 6480 | }
2023-04-26 1:15 [Bug c++/109629] New: internal compiler error: in final_scan_insn_1, at final.c:3078 6480 | } linus.zhu at mavenir dot com
` (6 preceding siblings ...)
2023-04-26 1:36 ` pinskia at gcc dot gnu.org
@ 2023-04-26 1:54 ` linus.zhu at mavenir dot com
2023-04-26 1:56 ` pinskia at gcc dot gnu.org
` (10 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: linus.zhu at mavenir dot com @ 2023-04-26 1:54 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109629
--- Comment #8 from Linus <linus.zhu at mavenir dot com> ---
hi Andrew, thanks. And before raising another ticket for attaching the second
half of ccdNSTWA.out, I did try to add one more attachment to this bug, but it
hinted that previous one will be obsolete.
Anyway it's not important, another part of ccdNSTWA.out was uploaded to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109630.
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug target/109629] internal compiler error: in final_scan_insn_1, at final.c:3078 6480 | }
2023-04-26 1:15 [Bug c++/109629] New: internal compiler error: in final_scan_insn_1, at final.c:3078 6480 | } linus.zhu at mavenir dot com
` (7 preceding siblings ...)
2023-04-26 1:54 ` linus.zhu at mavenir dot com
@ 2023-04-26 1:56 ` pinskia at gcc dot gnu.org
2023-04-26 1:59 ` linus.zhu at mavenir dot com
` (9 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: pinskia at gcc dot gnu.org @ 2023-04-26 1:56 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109629
--- Comment #9 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Linus from comment #8)
> hi Andrew, thanks. And before raising another ticket for attaching the
> second half of ccdNSTWA.out, I did try to add one more attachment to this
> bug, but it hinted that previous one will be obsolete.
No it will not. It says:
"(optional) Check each existing attachment made obsolete by your new
attachment."
See the optional part. It will only make it is obsolete if you chose to do
that.
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug target/109629] internal compiler error: in final_scan_insn_1, at final.c:3078 6480 | }
2023-04-26 1:15 [Bug c++/109629] New: internal compiler error: in final_scan_insn_1, at final.c:3078 6480 | } linus.zhu at mavenir dot com
` (8 preceding siblings ...)
2023-04-26 1:56 ` pinskia at gcc dot gnu.org
@ 2023-04-26 1:59 ` linus.zhu at mavenir dot com
2023-04-26 2:01 ` linus.zhu at mavenir dot com
` (8 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: linus.zhu at mavenir dot com @ 2023-04-26 1:59 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109629
--- Comment #10 from Linus <linus.zhu at mavenir dot com> ---
(In reply to Andrew Pinski from comment #5)
> /* If we have a length attribute, this instruction should have
> been split in shorten_branches, to ensure that we would have
> valid length info for the splitees. */
> gcc_assert (!HAVE_ATTR_length);
Yes, when I checked source code of gcc 11, I saw them.
And I saw:
"
Tue Mar 18 16:12:28 1997 Jim Wilson <wilson@cygnus.com>
* final.c (shorten_branches): Split all insns before computing insn
lengths.
(final_scan_insn, case default): If HAVE_ATTR_length defined, call
abort for any insn that has a '#' output template.
"
I just wait for your new response, right?
Thanks for checking the issue.
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug target/109629] internal compiler error: in final_scan_insn_1, at final.c:3078 6480 | }
2023-04-26 1:15 [Bug c++/109629] New: internal compiler error: in final_scan_insn_1, at final.c:3078 6480 | } linus.zhu at mavenir dot com
` (9 preceding siblings ...)
2023-04-26 1:59 ` linus.zhu at mavenir dot com
@ 2023-04-26 2:01 ` linus.zhu at mavenir dot com
2023-04-26 2:02 ` pinskia at gcc dot gnu.org
` (7 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: linus.zhu at mavenir dot com @ 2023-04-26 2:01 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109629
--- Comment #11 from Linus <linus.zhu at mavenir dot com> ---
(In reply to Andrew Pinski from comment #9)
> (In reply to Linus from comment #8)
> > hi Andrew, thanks. And before raising another ticket for attaching the
> > second half of ccdNSTWA.out, I did try to add one more attachment to this
> > bug, but it hinted that previous one will be obsolete.
>
> No it will not. It says:
> "(optional) Check each existing attachment made obsolete by your new
> attachment."
> See the optional part. It will only make it is obsolete if you chose to do
> that.
Thanks for the clarification.
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug target/109629] internal compiler error: in final_scan_insn_1, at final.c:3078 6480 | }
2023-04-26 1:15 [Bug c++/109629] New: internal compiler error: in final_scan_insn_1, at final.c:3078 6480 | } linus.zhu at mavenir dot com
` (10 preceding siblings ...)
2023-04-26 2:01 ` linus.zhu at mavenir dot com
@ 2023-04-26 2:02 ` pinskia at gcc dot gnu.org
2023-04-26 2:11 ` linus.zhu at mavenir dot com
` (6 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: pinskia at gcc dot gnu.org @ 2023-04-26 2:02 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109629
--- Comment #12 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Linus from comment #10)
> (In reply to Andrew Pinski from comment #5)
> > /* If we have a length attribute, this instruction should have
> > been split in shorten_branches, to ensure that we would have
> > valid length info for the splitees. */
> > gcc_assert (!HAVE_ATTR_length);
>
> Yes, when I checked source code of gcc 11, I saw them.
> I just wait for your new response, right?
> Thanks for checking the issue.
No, I was just pointing out where the ICE is happening. But really it is
something inside the target backend's md file. Still need to reduce/debug it to
figure out which pattern is not being split.
Also Please FILE this with redhat since this is a redhat modified compiler
first.
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug target/109629] internal compiler error: in final_scan_insn_1, at final.c:3078 6480 | }
2023-04-26 1:15 [Bug c++/109629] New: internal compiler error: in final_scan_insn_1, at final.c:3078 6480 | } linus.zhu at mavenir dot com
` (11 preceding siblings ...)
2023-04-26 2:02 ` pinskia at gcc dot gnu.org
@ 2023-04-26 2:11 ` linus.zhu at mavenir dot com
2023-04-26 2:16 ` linus.zhu at mavenir dot com
` (5 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: linus.zhu at mavenir dot com @ 2023-04-26 2:11 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109629
--- Comment #13 from Linus <linus.zhu at mavenir dot com> ---
(In reply to Andrew Pinski from comment #12)
> (In reply to Linus from comment #10)
> > (In reply to Andrew Pinski from comment #5)
> > > /* If we have a length attribute, this instruction should have
> > > been split in shorten_branches, to ensure that we would have
> > > valid length info for the splitees. */
> > > gcc_assert (!HAVE_ATTR_length);
> >
> > Yes, when I checked source code of gcc 11, I saw them.
>
> > I just wait for your new response, right?
> > Thanks for checking the issue.
>
> No, I was just pointing out where the ICE is happening. But really it is
> something inside the target backend's md file. Still need to reduce/debug it
> to figure out which pattern is not being split.
>
> Also Please FILE this with redhat since this is a redhat modified compiler
> first.
Okay and thanks.
Is there a chance that this issue will be gone if I try the original gcc 9 or
gcc 10?
By the way, same code didn't survive aarch64 gcc 9.3.1, but did survive X86 gcc
9.3.1.
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug target/109629] internal compiler error: in final_scan_insn_1, at final.c:3078 6480 | }
2023-04-26 1:15 [Bug c++/109629] New: internal compiler error: in final_scan_insn_1, at final.c:3078 6480 | } linus.zhu at mavenir dot com
` (12 preceding siblings ...)
2023-04-26 2:11 ` linus.zhu at mavenir dot com
@ 2023-04-26 2:16 ` linus.zhu at mavenir dot com
2023-04-26 2:22 ` pinskia at gcc dot gnu.org
` (4 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: linus.zhu at mavenir dot com @ 2023-04-26 2:16 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109629
--- Comment #14 from Linus <linus.zhu at mavenir dot com> ---
devtoolset-9-gcc-9.3.1-2.2.el7.aarch64
devtoolset-9-gcc-9.3.1-2.el7.x86_64
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug target/109629] internal compiler error: in final_scan_insn_1, at final.c:3078 6480 | }
2023-04-26 1:15 [Bug c++/109629] New: internal compiler error: in final_scan_insn_1, at final.c:3078 6480 | } linus.zhu at mavenir dot com
` (13 preceding siblings ...)
2023-04-26 2:16 ` linus.zhu at mavenir dot com
@ 2023-04-26 2:22 ` pinskia at gcc dot gnu.org
2023-04-26 2:34 ` linus.zhu at mavenir dot com
` (3 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: pinskia at gcc dot gnu.org @ 2023-04-26 2:22 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109629
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |DUPLICATE
Status|WAITING |RESOLVED
--- Comment #15 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Already fixed.
*** This bug has been marked as a duplicate of bug 98136 ***
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug target/109629] internal compiler error: in final_scan_insn_1, at final.c:3078 6480 | }
2023-04-26 1:15 [Bug c++/109629] New: internal compiler error: in final_scan_insn_1, at final.c:3078 6480 | } linus.zhu at mavenir dot com
` (14 preceding siblings ...)
2023-04-26 2:22 ` pinskia at gcc dot gnu.org
@ 2023-04-26 2:34 ` linus.zhu at mavenir dot com
2023-04-26 2:41 ` pinskia at gcc dot gnu.org
` (2 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: linus.zhu at mavenir dot com @ 2023-04-26 2:34 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109629
--- Comment #16 from Linus <linus.zhu at mavenir dot com> ---
(In reply to Andrew Pinski from comment #15)
> Already fixed.
>
> *** This bug has been marked as a duplicate of bug 98136 ***
Thanks.
1. 98136 was fixed for gcc 9.2.0. So original gcc 10 includes the fix, right?
2. I still saw the issue with gcc 10 just because of the fix was not picked by
devtoolset-10-gcc-c++-10.2.1-11.2.el7.aarch64, right?
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug target/109629] internal compiler error: in final_scan_insn_1, at final.c:3078 6480 | }
2023-04-26 1:15 [Bug c++/109629] New: internal compiler error: in final_scan_insn_1, at final.c:3078 6480 | } linus.zhu at mavenir dot com
` (15 preceding siblings ...)
2023-04-26 2:34 ` linus.zhu at mavenir dot com
@ 2023-04-26 2:41 ` pinskia at gcc dot gnu.org
2023-04-26 2:57 ` linus.zhu at mavenir dot com
2023-04-26 2:59 ` pinskia at gcc dot gnu.org
18 siblings, 0 replies; 20+ messages in thread
From: pinskia at gcc dot gnu.org @ 2023-04-26 2:41 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109629
--- Comment #17 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Linus from comment #16)
> (In reply to Andrew Pinski from comment #15)
> > Already fixed.
> >
> > *** This bug has been marked as a duplicate of bug 98136 ***
>
> Thanks.
>
> 1. 98136 was fixed for gcc 9.2.0. So original gcc 10 includes the fix, right?
> 2. I still saw the issue with gcc 10 just because of the fix was not picked
> by devtoolset-10-gcc-c++-10.2.1-11.2.el7.aarch64, right?
It was NOT fixed in GCC 9.2.0 but rather 9.4.0; it was reported against 9.2.0
though.
The versions which incldue the fix: 10.4.0, 11.1.0, 8.5.0, 9.4.0 (and above
versions, e.g. 12.1.0).
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug target/109629] internal compiler error: in final_scan_insn_1, at final.c:3078 6480 | }
2023-04-26 1:15 [Bug c++/109629] New: internal compiler error: in final_scan_insn_1, at final.c:3078 6480 | } linus.zhu at mavenir dot com
` (16 preceding siblings ...)
2023-04-26 2:41 ` pinskia at gcc dot gnu.org
@ 2023-04-26 2:57 ` linus.zhu at mavenir dot com
2023-04-26 2:59 ` pinskia at gcc dot gnu.org
18 siblings, 0 replies; 20+ messages in thread
From: linus.zhu at mavenir dot com @ 2023-04-26 2:57 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109629
--- Comment #18 from Linus <linus.zhu at mavenir dot com> ---
(In reply to Andrew Pinski from comment #17)
> (In reply to Linus from comment #16)
> > (In reply to Andrew Pinski from comment #15)
> > > Already fixed.
> > >
> > > *** This bug has been marked as a duplicate of bug 98136 ***
> >
> > Thanks.
> >
> > 1. 98136 was fixed for gcc 9.2.0. So original gcc 10 includes the fix, right?
> > 2. I still saw the issue with gcc 10 just because of the fix was not picked
> > by devtoolset-10-gcc-c++-10.2.1-11.2.el7.aarch64, right?
>
> It was NOT fixed in GCC 9.2.0 but rather 9.4.0; it was reported against
> 9.2.0 though.
>
> The versions which incldue the fix: 10.4.0, 11.1.0, 8.5.0, 9.4.0 (and above
> versions, e.g. 12.1.0).
Great thanks, Andrew, for your time and effort.
By the way, same code didn't survive aarch64 gcc 9.3.1, but did survive X86 gcc
9.3.1 -- devtoolset-9-gcc-9.3.1-2.el7.x86_64.
Do you have any clue about it?
Again, thanks for the great support!
^ permalink raw reply [flat|nested] 20+ messages in thread
* [Bug target/109629] internal compiler error: in final_scan_insn_1, at final.c:3078 6480 | }
2023-04-26 1:15 [Bug c++/109629] New: internal compiler error: in final_scan_insn_1, at final.c:3078 6480 | } linus.zhu at mavenir dot com
` (17 preceding siblings ...)
2023-04-26 2:57 ` linus.zhu at mavenir dot com
@ 2023-04-26 2:59 ` pinskia at gcc dot gnu.org
18 siblings, 0 replies; 20+ messages in thread
From: pinskia at gcc dot gnu.org @ 2023-04-26 2:59 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109629
--- Comment #19 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Linus from comment #18)
> By the way, same code didn't survive aarch64 gcc 9.3.1, but did survive X86
> gcc 9.3.1 -- devtoolset-9-gcc-9.3.1-2.el7.x86_64.
> Do you have any clue about it?
Yes it is a target specific issue. Again if you want a fix for these
devtoolset, please talk with Redhat, we don't support them here.
^ permalink raw reply [flat|nested] 20+ messages in thread