public inbox for dwz@sourceware.org
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: Mark Wielaard <mark@klomp.org>
Cc: dwz@sourceware.org, jakub@redhat.com
Subject: Re: [PATCH] Document experimental status of odr
Date: Fri, 26 Feb 2021 14:25:57 +0100	[thread overview]
Message-ID: <bc5e64d7-8ba7-9c2c-db24-70999621a59d@suse.de> (raw)
In-Reply-To: <20210226130453.GE3014@wildebeest.org>

On 2/26/21 2:04 PM, Mark Wielaard wrote:
> Hi Tom,
> 
> On Thu, Feb 25, 2021 at 05:17:31PM +0100, Tom de Vries wrote:
>> Add documentation of the experimental status of the odr optimization in dwz.1.
>>
>> Any comments?
>>
>>
>> 	PR dwz/27401
>> 	* dwz.1: Document experimental status of odr.
> 
> Looks good to me.
> 

Thanks for the review.

> BTW. Do you already know when would you consider it no longer
> experimental? Are there still fundemental bugs/design issues

With the current state of trunk + recently submitted odr fixes there are
no longer any known bugs in odr.

The only design issue that I can think of is that it's disabled for
low-mem (listed in set_die_odr_state as todo).

> or is it
> now just having people experiment with it and finding bugs?

That as well.

[ FWIW, I've unofficially labeled a recent commit as 0.14-rc1 and am in
the process of bringing that + submitted odr fixes to tumbleweed, with
odr enabled by default.  So, I expect some feedback there ... ;) ]

To come back to your question, the label experimental is to warn the
user that it can be used, but expect problems.  So I'd say once we fix
the initially reported problems and figure out the low-mem thingy, we
can drop the experimental label.

Thanks,
- Tom

      reply	other threads:[~2021-02-26 13:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-25 16:17 Tom de Vries
2021-02-26 13:04 ` Mark Wielaard
2021-02-26 13:25   ` Tom de Vries [this message]

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=bc5e64d7-8ba7-9c2c-db24-70999621a59d@suse.de \
    --to=tdevries@suse.de \
    --cc=dwz@sourceware.org \
    --cc=jakub@redhat.com \
    --cc=mark@klomp.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).