From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 709213856DE8; Tue,  2 Aug 2022 13:14:34 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 709213856DE8
From: "kloczko.tomasz at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/106499] LTO runs forever in libfabric 1.15.1 linking
Date: Tue, 02 Aug 2022 13:14:34 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: compile-time-hog, memory-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kloczko.tomasz at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-106499-4-d6GOa8NftG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-106499-4@http.gcc.gnu.org/bugzilla/>
References: <bug-106499-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2022 13:14:34 -0000

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

--- Comment #17 from Tomasz K=C5=82oczko <kloczko.tomasz at gmail dot com> =
---
(In reply to Martin Li=C5=A1ka from comment #16)
[..]
> Well, in most cases it's used for symbol versioning which is implemented =
by
> assembly directives. However, we offer symver function attribute that
> survives LTO partitioning. One more reason can be usage of top-level asm,
> which can be mitigated by -fno-lto for units that use it.

Yes I know however many project still is not usig that macro.

BTW I just realised that as long as low level versioning symbols is handled=
 it
turns ouit that this bug seems is only arount he code which is handling
versioned symbols taken from sym file.

It should not be so hard to fix that. Am I right?
This bug is in the queue for et least two years. What is the difficultu with
fixing that?=