public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "mjw at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/17959] Something (broken DWARF?) causes Systemtap to generate C code with uint0_t types
Date: Thu, 09 Apr 2015 14:56:00 -0000	[thread overview]
Message-ID: <bug-17959-6586-v8ajkeZDGA@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17959-6586@http.sourceware.org/bugzilla/>

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

Mark Wielaard <mjw at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #4 from Mark Wielaard <mjw at redhat dot com> ---
commit 4bfa7779843bda6f74c547a42a092a2974d07b9e
Author: Mark Wielaard <mjw@redhat.com>
Date:   Thu Apr 9 16:51:56 2015 +0200

    PR17959 Allow size-less pointer types.

    golang might produce a DW_TAG_pointer_type without any size. Assume
    the size of the pointer is equal to the address size of the DWARF CU
    in that case. Otherwise we might try to create values of type uint0_t.

-- 
You are receiving this mail because:
You are the assignee for the bug.

      parent reply	other threads:[~2015-04-09 14:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-11 15:36 [Bug translator/17959] New: " aram.h at mgk dot ro
2015-02-11 15:38 ` [Bug translator/17959] " aram.h at mgk dot ro
2015-02-11 20:32 ` aram.h at mgk dot ro
2015-02-11 20:33 ` aram.h at mgk dot ro
2015-02-11 21:18 ` mjw at redhat dot com
2015-04-09 14:56 ` mjw at redhat dot com [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=bug-17959-6586-v8ajkeZDGA@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=systemtap@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).