public inbox for dwz@sourceware.org
 help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/27561] New: low-mem odr
Date: Thu, 11 Mar 2021 13:30:35 +0000	[thread overview]
Message-ID: <bug-27561-11298@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=27561

            Bug ID: 27561
           Summary: low-mem odr
           Product: dwz
           Version: unspecified
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: default
          Assignee: nobody at sourceware dot org
          Reporter: vries at gcc dot gnu.org
                CC: dwz at sourceware dot org
  Target Milestone: ---

Atm odr is disabled in low-mem mode, here in set_die_odr_state:
...
  if (low_mem)                                                                  
    /* Todo: allow low-mem mode.  */                                            
    return;                                                                    
             ...

In principle, we could enable this.

When doing the enable-and-see-what-breaks approach, we get a few easy things to
fix.  Using --devel-verify-dups also helps.  But after that, we run into harder
problems.

ISTM that enabling this only makes sense in a setup where all accesses of
struct dw_die fields after die_parent (so, the ones that are conditionally
available) can be (optionally) instrumented such that it's checked whether the
field is indeed available.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2021-03-11 13:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-11 13:30 vries at gcc dot gnu.org [this message]
2021-03-11 14:07 ` [Bug default/27561] [dwz] " vries 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-27561-11298@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=dwz@sourceware.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).