From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id E7D48385B836; Tue, 31 Mar 2020 15:22:03 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E7D48385B836 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1585668123; bh=nb15niQYpcBjPMAsTDq/pIzxelss3kqg4en/XkacWfc=; h=From:To:Subject:Date:In-Reply-To:References:From; b=u23B0lylmshRtx78vzc+S3uegmA9X2kAOD3vwlZEMzTPtS2YgGoIist3BpXxK8JB/ zPAgVDsTOp7yL4mUEmZ9Yy4oSKTzkzPFlx0+YPGNiqVxC19SXtP5Nk5feLLfmBRXms FyJisAgIcnbKCsbcLwvGfQ4kIyWkpxKoKeZExHb8= From: "andrew at ishiboo dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/89096] [8/9/10 regression] AIX 7 linker rejects _.ro_ sections by default Date: Tue, 31 Mar 2020 15:22:02 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 8.2.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: andrew at ishiboo dot com X-Bugzilla-Status: WAITING X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 8.5 X-Bugzilla-Flags: 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: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2020 15:22:04 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D89096 --- Comment #26 from Andrew Paprocki --- Just re-summarizing now for 2020 since there have been a few twists and tur= ns and distractions. This issue has nothing to do with CMake, -brtl, or -bexpall linker flags. T= his issue only occurs when GCC is told to pass the -bsvr4 linker flag, because = the application wishes to use multiple -R parameters as documented in the man p= age (see comment 14). When that occurs, the error in this ticket happens. The already applied patches to GCC mentioned throughout the bug do not chan= ge any behavior -- it still fails to link. David, can you or someone on the linker team determine if this is an issue = with the GCC side of things, or it is simply a bug in the linker? It is difficult for an outsider to determine if this is purely on the linker side or if GCC= is not conforming somehow to what the linker expects.=