From: Richard Biener <rguenther@suse.de>
To: Diego Novillo <dnovillo@google.com>, Richard Earnshaw <rearnsha@arm.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Ian Lance Taylor <iant@google.com>,
Lawrence Crowl <crowl@google.com>,
Laurynas Biveinis <laurynas.biveinis@gmail.com>
Subject: Re: RFA - Remove GC zone allocator
Date: Wed, 23 Jan 2013 14:31:00 -0000 [thread overview]
Message-ID: <72a04a5e-7da6-4809-a9a8-b5ecffd01351@email.android.com> (raw)
In-Reply-To: <CAD_=9DS+EmKDG7cG8gBT9Bz+Kw-5QEjW5gtiU4s+8Mae1eDDNA@mail.gmail.com>
Diego Novillo <dnovillo@google.com> wrote:
>On Wed, Jan 23, 2013 at 4:19 AM, Richard Earnshaw <rearnsha@arm.com>
>wrote:
>
>> Won't this mean that use of the configure option is now silently
>ignored,
>> rather than generating an error? Existing users of the option might
>be
>> slightly confused by that.
>
>That's true. Perhaps a warning message stating that --with-gc is now
>ignored? Or would you prefer a straight out error?
I don't think we ever cared for this.
Thus, the patch is ok if no other rm objects within a day.
Thanks,
Richard.
>
>Diego.
next prev parent reply other threads:[~2013-01-23 14:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 14:33 Diego Novillo
2013-01-23 9:20 ` Richard Earnshaw
2013-01-23 12:03 ` Diego Novillo
2013-01-23 14:31 ` Richard Biener [this message]
2013-01-23 14:33 ` Jakub Jelinek
2013-01-24 15:16 ` Diego Novillo
2023-07-04 15:58 ` GGC: Remove unused 'bool is_string' arguments to 'ggc_pch_{count,alloc,write}_object' (was: RFA - Remove GC zone allocator) Thomas Schwinge
2023-07-05 6:18 ` Richard Biener
2013-01-23 11:29 ` RFA - Remove GC zone allocator Laurynas Biveinis
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=72a04a5e-7da6-4809-a9a8-b5ecffd01351@email.android.com \
--to=rguenther@suse.de \
--cc=crowl@google.com \
--cc=dnovillo@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iant@google.com \
--cc=laurynas.biveinis@gmail.com \
--cc=rearnsha@arm.com \
/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).