[Bug target/96893] New: aarch64:Segmentation fault signal terminated program cc1

[Bug target/96893] New: aarch64:Segmentation fault signal terminated program cc1

[z.zhanghaijian at huawei dot com]

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

            Bug ID: 96893
           Summary: aarch64:Segmentation fault signal terminated program
                    cc1
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: z.zhanghaijian at huawei dot com
  Target Milestone: ---

The case like:
test.c:
int f300001() { }
 void f300000() {       printf("300000\n");     f300001(); }
 void f299999() {       printf("299999\n");     f300000(); }
 void f299998() {       printf("299998\n");     f299999(); }
 void f299997() {       printf("299997\n");     f299998(); }
...
 void f10() {   printf("10\n");         f11(); }
 void f9() {    printf("9\n");  f10(); }
 void f8() {    printf("8\n");  f9(); }
 void f7() {    printf("7\n");  f8(); }
 void f6() {    printf("6\n");  f7(); }
 void f5() {    printf("5\n");  f6(); }
 void f4() {    printf("4\n");  f5(); }
 void f3() {    printf("3\n");  f4(); }
 void f2() {    printf("2\n");  f3(); }
 void f1() {    printf("1\n");  f2(); }
 int main(int argc, char** argv){       f1(); }

This produces the error on aarch64:

gcc test.c -S -w
gcc: internal compiler error: Segmentation fault signal terminated program cc1
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://gcc.gnu.org/bugs/> for instructions.

gcc version 11.0.0 20200902 (experimental) (GCC)

[Bug target/96893] aarch64:Segmentation fault signal terminated program cc1

[rguenth at gcc dot gnu.org]

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2020-09-02
             Target|                            |aarch64
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |WAITING

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Please provide a script to generate the testcase.  A backtrace would be nice as
well, likely the stack blows up.

[Bug target/96893] aarch64:Segmentation fault signal terminated program cc1

[z.zhanghaijian at huawei dot com]

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

--- Comment #2 from z.zhanghaijian at huawei dot com <z.zhanghaijian at huawei dot com> ---
(In reply to Richard Biener from comment #1)
> Please provide a script to generate the testcase.  A backtrace would be nice
> as well, likely the stack blows up.

cat gen.sh
#!/bin/bash
echo 'int f3000001() { }' > test.c
for i in {300000..1}
do
        j=$(($i+1))
        echo "void f$i() {    printf(\"$i\\n\");  f$j(); }" >> test.c
done
echo "int main(int argc, char** argv){       f1(); }" >> test.c

The script can generate the testcase.

[Bug target/96893] aarch64:Segmentation fault signal terminated program cc1

[marxin at gcc dot gnu.org]

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

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

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

--- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
Confirmed, it's a stack overflow and it happens only on x86_64.
I'm trying to reduce that.

[Bug target/96893] aarch64:Segmentation fault signal terminated program cc1

[marxin at gcc dot gnu.org]

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |NEW

--- Comment #4 from Martin Liška <marxin at gcc dot gnu.org> ---
It's hard to reduce, but one can see a stack overflow in GGC collect.