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 47ADE3844012; Wed, 11 Aug 2021 21:57:01 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 47ADE3844012
From: "mailboxnotfound at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/101843] Build of binutils-2.37 with gcc-11.2.0 fails
 due to change to libiberty/hashtab.c
Date: Wed, 11 Aug 2021 21:57:01 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 11.2.0
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mailboxnotfound at yahoo dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
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-101843-4-zcDG74CR40@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-101843-4@http.gcc.gnu.org/bugzilla/>
References: <bug-101843-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: Wed, 11 Aug 2021 21:57:01 -0000

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

--- Comment #6 from john henning <mailboxnotfound at yahoo dot com> ---
Let's simplify.

Per Richard's comment #1, there won't be a code fix.  OK.=20=20
As to a doc fix, Richard wrote:=20

  "For release versions your milage may vary and we fail to document working
version pairs"

YES - it would be nice if working pairs were documented in a list somewhere.
BUT - it might also be difficult to keep such a list updated.

So let's simplify.  How about if=20
      https://gcc.gnu.org/install/download.html=20
were to just include the generic advice that if you want to build them
together, then you should pick versions that were developed at about the sa=
me
timeframe.

(Yes, this is obvious advice once you understand that they have common
subdirectories, such as libiberty/.  But it was not obvious to at least one
user; and if that advice had been present, the user might have avoided a si=
de
track.)

I've started to bat around possible specific language and perhaps will prop=
ose
a specific patch along these lines.=