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 47D713858CD1; Mon, 18 Mar 2024 10:50:51 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 47D713858CD1
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1710759051;
	bh=QeJ0X1gbK3Ok+wgJIQzOr/N34Aaq4xRjZ/RFOgcTVfs=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=wRrwlC3GomNc2HjG1w9q+UIVQwHL4dLNclAi4DWrn8LDwjCADetraH9gapQkkojhW
	 wPjmbzaiy+nFdgN/Paa/e/uhcK+6KWIg8RsIRV7DjNe4xIscV58ZqMRC+PoPav7+bW
	 vwIgmxXRK0v1BOK42qLnduOKmFSXO2E8vNKX4pAQ=
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libobjc/48626] --enable-objc-gc should be automatic
Date: Mon, 18 Mar 2024 10:50:49 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libobjc
X-Bugzilla-Version: 4.7.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ro at CeBiTec dot Uni-Bielefeld.DE
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: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-48626-4-JHm72xRWXS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-48626-4@http.gcc.gnu.org/bugzilla/>
References: <bug-48626-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
List-Id: <gcc-bugs.sourceware.org>

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

--- Comment #8 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot U=
ni-Bielefeld.DE> ---
> --- Comment #7 from Iain Sandoe <iains at gcc dot gnu.org> ---
> now that boehm-gc is no longer in tree
>
> what should we do with this?
>
> I suppose there could be some more sophisticated top-level configuration
> (similar to GMP et. al.) which determines if there's a suitable libgc
> available?

On the contrary: I think support for --enable-objc-gc at both the
toplevel and gcc can just go.

* At the toplevel, it's just a preliminary check which I don't think is
  necessary at all since it's redone in more detail in libobjc.

* In gcc, all that --enable-objc-gc does is set OBJC_BOEHM_GC in
  gcc/Makefile, which isn't ever used.=