Bug 2041667 - Regression: infinite loop in add_sibling_attributes
Summary: Regression: infinite loop in add_sibling_attributes
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gcc
Version: 36
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-18 03:08 UTC by Björn Persson
Modified: 2023-05-25 16:51 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-25 16:51:35 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Fedora Pagure releng issue 10540 0 None None None 2022-01-18 03:08:38 UTC

Description Björn Persson 2022-01-18 03:08:38 UTC
Description of problem:
In GCC 12, Certain Ada source files trigger what looks like infinite tail recursion in add_sibling_attributes in dwarf2out.c. This does not happen in GCC 11. It seems to be specific to 64-bit arches.

I don't have a minimal reproducer yet. When building GPRbuild, the problem is triggered by gprbind.adb and gpr-knowledge.adb. Here's an example of a GCC invocation from the package build:

/usr/bin/gcc -c -x ada -gnatA -gnat12 -gnaty -gnatQ -gnata -g -gnata -gnatVa -gnatwaCJI -gnatwe -gnatyg -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -gnatn -gnat-p -gnatVd -gnatwn -gnatyN -gnatec=/tmp/GNAT-TEMP-000010.TMP -gnatec=/home/fedora/rombobeorn/rpmbuild/BUILD/gprbuild-2020-20200429-19BD2-src/gpr/debug.adc -gnatem=/tmp/GNAT-TEMP-000011.TMP /home/fedora/rombobeorn/rpmbuild/BUILD/gprbuild-2020-20200429-19BD2-src/gpr/src/gpr-knowledge.adb

Version-Release number of selected component (if applicable):
12.0.0-0.5.fc36

How reproducible:
It seems deterministic. The problem is triggered by the same two source files every time on x86-64. Builds on aarch64, ppc64le and s390x also get stuck but I don't know the details. The problem does not seem to occur on i686 or armv7hl.

Steps to Reproduce:
1. Rebuild the gprbuild package in Rawhide. If _smp_build_ncpus <= 2, then the whole build gets stuck when two gnat1 processes are looping. Otherwise compilation in parallel continues until all the other source files are done and only the two looping processes remain.
2. Run gdb -p with the PID of one of the looping gnat1 processes.

Comment 1 Ben Cotton 2022-02-08 21:10:41 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle.
Changing version to 36.

Comment 2 Ben Cotton 2023-04-25 16:47:36 UTC
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '36'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 3 Ludek Smid 2023-05-25 16:51:35 UTC
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16.

Fedora Linux 36 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.