From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp26.services.sfr.fr (smtp26.services.sfr.fr [93.17.128.196]) by sourceware.org (Postfix) with ESMTPS id B9A0C385C41B for ; Tue, 30 Aug 2022 18:53:17 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org B9A0C385C41B Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=neuf.fr Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=neuf.fr X-mail-filterd: {"version":"1.3.4","queueID":"4MHGfM171Dz1LQKdB","contextId":"aec59bd2-57d0-4bd8-8af6-c51d4e173b27"} Received: from [192.168.1.11] (91-171-27-54.subs.proxad.net [91.171.27.54]) by msfrf2612.sfr.fr (SMTP Server) with ESMTP id 4MHGfM171Dz1LQKdB; Tue, 30 Aug 2022 20:53:15 +0200 (CEST) X-mail-filterd: {"version":"1.3.4","queueID":"4MHGfL5tTPz1LQKcj","contextId":"0fd07ef7-c3b4-42cd-b783-ef1352099ca1"} X-sfr-mailing: LEGIT X-sfr-spamrating: 40 X-sfr-spam: not-spam DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=neuf.fr; s=202006; t=1661885595; h=Subject:From:To:Cc:Date:In-Reply-To:References; bh=+dXyzCHRlM iRWQk0R2znL8UyEO+EDg61O5jTqwdmaZE=; b=bse9ae0KFp3kSMPFK6y8JQEMLWJwYpfiA8oWH3 h0zGtveMD3a+OesAzcKQj1gbkFhuE9VeN/aOO51C2dAOnw1ilCHNnIGipmPy1eKIIma/v7+aEWjy aLz3jpCkahYN750PsYBvMVeIK2+ZH9WLeJzWHgDN5GLF/Q8P+CXxMew++sdh0yBmoHGZ9kuo4bTH txzbO4d6a/2m8KnIXrZM4lJm+b5QfienFtETgx1asqKR4ildGmdS9s8y0at+hCaOYMn054FjBao9 aoqvktcvRW9QV6Fd+/3llXOKzgSaWd9WJTX9q/6Egw4eaN/eujBHXIlIQLD4vwCEVZGzgyrxQtBA == Received: from [192.168.1.11] (91-171-27-54.subs.proxad.net [91.171.27.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: pierre.labastie@neuf.fr) by msfrf2612.sfr.fr (SMTP Server) with ESMTPSA id 4MHGfL5tTPz1LQKcj; Tue, 30 Aug 2022 20:53:14 +0200 (CEST) Authentication-Results: sfr.fr; auth=pass (LOGIN) smtp.auth=pierre.labastie@neuf.fr Message-ID: Subject: Re: question: i386 ld.gold reports "internal error" linking files with SHT_RELA section From: Pierre Labastie To: "H.J. Lu" , Xi Ruoyao Cc: Binutils Date: Tue, 30 Aug 2022 20:53:14 +0200 In-Reply-To: References: <199ec63c39a4a323e93402277c1cc67f5c8216bf.camel@xry111.site> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.44.4 MIME-Version: 1.0 X-Spam-Status: No, score=1.3 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,JMQ_SPF_NEUTRAL,RCVD_IN_BARRACUDACENTRAL,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE,WEIRD_PORT autolearn=no autolearn_force=no version=3.4.6 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On Tue, 2022-08-30 at 11:21 -0700, H.J. Lu wrote: > On Tue, Aug 30, 2022 at 7:39 AM Xi Ruoyao via Binutils > wrote: > >=20 > > Building SeaMonkey on i686 results: > >=20 > > =C2=A0=C2=A0=C2=A0 "/usr/bin/ld.gold: internal error in relocate_sectio= n, at > > ../../gold/i386.cc:3683" > >=20 > > i386.cc:3683 is: > >=20 > > =C2=A0=C2=A0=C2=A0 gold_assert(sh_type =3D=3D elfcpp::SHT_REL); > >=20 > > AFAIK i386 normally use SHT_REL and x86_64 normally use SHT_RELA.=C2=A0= But > > we've found that nasm-2.15.05 generates SHT_RELA for i386 as well. > >=20 > > So should SHT_RELA be allowed for i386 at all?=C2=A0 If "yes" we should= fix > > it for gold, if "no" we should fix it for nasm. > > -- > > Xi Ruoyao > > School of Aerospace Science and Technology, Xidian University >=20 > =C2=A0SHT_RELA shouldn't be used for i386. >=20 But it is accepted by ld.bfd... FWIIW, only the dwarf debug sections are generated as SHT_RELA by nasm. Pierre Labastie