public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug libdw/28294] dwarf_aggregate_size fails on some array types
Date: Mon, 18 Oct 2021 11:39:18 +0000	[thread overview]
Message-ID: <bug-28294-10460-sWJ20aipkq@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28294-10460@http.sourceware.org/bugzilla/>

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

--- Comment #4 from Mark Wielaard <mark at klomp dot org> ---
Pushed as:

commit c3a6a9dfc6ed0c24ab2d11b2d71f425b479575c9
Author: Mark Wielaard <mark@klomp.org>
Date:   Wed Oct 6 22:41:29 2021 +0200

    libdw: Use signedness of subrange type to determine array bounds

    When calculating the array size check if the subrange has an associate
    type, if it does then check the type to determine whether the upper
    and lower values need to be interpreted as signed of unsigned
    values. We default to signed because that is what the testcase
    run-aggregate-size.sh testfile-size4 expects (this is an hardwritten
    testcase, we could have chosen a different default).

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

    Signed-off-by: Mark Wielaard <mark@klomp.org>

Please reopen or file a new bug if this didn't fully resolve your issue.

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

  parent reply	other threads:[~2021-10-18 11:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-31 11:51 [Bug libdw/28294] New: " egb.atos at gmail dot com
2021-09-11 23:39 ` [Bug libdw/28294] " mark at klomp dot org
2021-09-11 23:43 ` mark at klomp dot org
2021-10-06 20:42 ` mark at klomp dot org
2021-10-18 11:39 ` mark at klomp dot org [this message]
2021-10-18 11:43 ` mark at klomp dot 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-28294-10460-sWJ20aipkq@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=elfutils-devel@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).