From owner-freebsd-toolchain@freebsd.org Mon May 20 20:38:15 2019 Return-Path: Delivered-To: freebsd-toolchain@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F3F371591D1A for ; Mon, 20 May 2019 20:38:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 835E4914F1 for ; Mon, 20 May 2019 20:38:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 3D1C11591D18; Mon, 20 May 2019 20:38:14 +0000 (UTC) Delivered-To: toolchain@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 00D8A1591D17 for ; Mon, 20 May 2019 20:38:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 789B4914EC for ; Mon, 20 May 2019 20:38:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id B8DF56DAC for ; Mon, 20 May 2019 20:38:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x4KKcCEa079785 for ; Mon, 20 May 2019 20:38:12 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x4KKcC0J079784 for toolchain@FreeBSD.org; Mon, 20 May 2019 20:38:12 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: toolchain@FreeBSD.org Subject: [Bug 237068] /usr/local/bin/ld: BFD (GNU Binutils) 2.30 assertion fail elflink.c:2824 Date: Mon, 20 May 2019 20:38:12 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: needs-qa X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: marklmi26-fbsd@yahoo.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: toolchain@FreeBSD.org X-Bugzilla-Flags: mfc-stable11? mfc-stable12? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 May 2019 20:38:15 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237068 --- Comment #19 from Mark Millard --- (In reply to Mark Millard from comment #16) The below is about alternate fixed_seed_override definitions/declarations in the small example (not llvm60) and the consequences, in particular not getting the BFD_ASSERTs. They are not proposed fixes: I'm just reporting what was important about the fixed_seed_override definition that I used in the small example. Instead: unsigned long fixed_seed_override=3D 0x0; or: extern unsigned long fixed_seed_override; so they instead do not contribute to .data . These change small_link_failure-1.0.so such that the BFD_ASSERT messages are not produced. The "0xdeadc0de" vs. other two end up as reported below. The file offset changes from as seen in (note the matching 0x10cc8 vs. the symbol tables for the 0xdeadc0de based example): . . . [19] .data PROGBITS 0000000000010ca8 00000ca8 0000000000000020 0000000000000000 WA 0 0 8 [20] .bss NOBITS 0000000000010cc8 00000cc8 0000000000000010 0000000000000000 WA 0 0 8 . . . Symbol table (.dynsym) contains 16 entries: Num: Value Size Type Bind Vis Ndx Name . . . 7: 0000000000010cc8 0 NOTYPE GLOBAL DEFAULT 20 __bss_start@@LLVM_6.0 (2) . . . Symbol table (.symtab) contains 52 entries: Num: Value Size Type Bind Vis Ndx Name . . . 43: 0000000000010cc8 0 NOTYPE GLOBAL DEFAULT 20 __bss_start . . . to as seen in (note the 0x10cc0 vs. 0x10cb9's in the symbol tables): . . . [19] .data PROGBITS 0000000000010ca8 00000ca8 0000000000000011 0000000000000000 WA 0 0 8 [20] .bss NOBITS 0000000000010cc0 00000cb9 0000000000000018 0000000000000000 WA 0 0 8 . . . Symbol table (.dynsym) contains 16 entries: Num: Value Size Type Bind Vis Ndx Name . . . 7: 0000000000010cb9 0 NOTYPE GLOBAL DEFAULT 20 __bss_start@@LLVM_6.0 (2) . . . Symbol table (.symtab) contains 52 entries: Num: Value Size Type Bind Vis Ndx Name . . . 43: 0000000000010cb9 0 NOTYPE GLOBAL DEFAULT 20 __bss_start . . . (Also note the odd .data size 0x11 compared to the earlier 0x20.) So the definition of fixed_seed_override with a non-zero value being involved is an important part of setting up the small example of rejecting __bss_start@@LLVM_6.0 use internally. (I had to discover this to make the small example C++ program.) --=20 You are receiving this mail because: You are the assignee for the bug.=