public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libobjc/48626] --enable-objc-gc should be automatic
Date: Tue, 24 May 2022 15:40:19 +0000	[thread overview]
Message-ID: <bug-48626-4-Z2OHEtckba@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48626-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Eric Gallager from comment #4)
> (In reply to Eric Gallager from comment #3)
> > I'll probably keep --enable-objc-gc in my configure flags anyways even if it
> > becomes automatic, but becoming automatic could help increase test coverage
> > of it. I guess I'll confirm this.
> 
> Note that Iain Sandoe generally prefers configure detecting things
> automatically instead of requiring additional flags; I'm not quite sure how
> to go about making this one automatic now that boehm-gc is no longer
> in-tree, though.

this seems to be another set of crossed wires.

Darwin only ever used boehm-gc for Java, not for NeXT ObjC

the configure option is related to GC for the GNU runtime.  In that case, the
configuration should work the same as it does for Linux.

===

The NeXT GC support (if it was implemented, which it isn't) on Darwin uses
system-provided libraries (libauto.dylib).  Objective-C GC was retired sometime
around darwin16, so the motivation is low to put effort into implementing it
ahead of more critical missing pieces.

  parent reply	other threads:[~2022-05-24 15:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-15 16:51 [Bug libobjc/48626] New: " ro at gcc dot gnu.org
2022-05-24 15:10 ` [Bug libobjc/48626] " egallager at gcc dot gnu.org
2022-05-24 15:40 ` iains at gcc dot gnu.org [this message]
2022-05-24 17:03 ` iains at gcc dot gnu.org
2024-03-17  5:20 ` iains at gcc dot gnu.org
2024-03-18 10:50 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-03-18 18:03 ` pinskia at gcc dot gnu.org
2024-03-19  9:35 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-03-19 10:40 ` doko at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-48626-4-Z2OHEtckba@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).