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 97F223877030; Sat, 21 Mar 2020 17:44:30 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 97F223877030
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
 s=default; t=1584812670;
 bh=aeWDlvq76fThHVZ9ttDoNUEKYykufB3D9WNA807vypo=;
 h=From:To:Subject:Date:In-Reply-To:References:From;
 b=BOxX33/ZxWzx+Y+sExn9aWOhWdsKa6iF/yyzZzclrrtLLNoyhkAJNRho0ZskSbU7M
 kgMLiJqx4un/kcCl4JOtAuL1Or46Bx3Ejlks2rWRvfK0BCgSPmLXXJQa9thmXdNujR
 UFmNQHb7Ts5LOCw+LC6wu3fU0UFZLgxyem3mdQo0=
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/94249] [10 regression] Many -flto -fuse-linker-plugin tests
 FAIL: could not add symbols
Date: Sat, 21 Mar 2020 17:44:30 +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: 10.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: everconfirmed bug_status cf_reconfirmed_on
Message-ID: <bug-94249-4-p6n5KaSEsw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-94249-4@http.gcc.gnu.org/bugzilla/>
References: <bug-94249-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: <http://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <http://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: <http://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Mar 2020 17:44:30 -0000

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

Martin Li=C5=A1ka <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2020-03-21

--- Comment #1 from Martin Li=C5=A1ka <marxin at gcc dot gnu.org> ---
It will be definitely caused by my g:c8429c2aba80f845939ffa6b2cfe8a0be1b500=
78.

The error comes from lto-plugin.c:

      if (add_symbols_v2)
        status =3D add_symbols_v2 (file->handle, lto_file.symtab.nsyms,
                                 lto_file.symtab.syms);
      else
        status =3D add_symbols (file->handle, lto_file.symtab.nsyms,
                              lto_file.symtab.syms);
      check (status =3D=3D LDPS_OK, LDPL_FATAL, "could not add symbols");

In our case add_symbols_v2 should be NULL, so the old function add_symbols
should be called.

So is the reason usage of ld.gold? Is the default linker fine?=