From: Mark H Weaver <mhw@netris.org>
To: William S Fulton <wsf@fultondesigns.co.uk>
Cc: 18711-done@debbugs.gnu.org
Subject: bug#18711: Numerous unknown attribute '__alloc_size__' warnings when using clang
Date: Wed, 15 Oct 2014 12:39:54 -0400 [thread overview]
Message-ID: <877g0170dh.fsf@yeeloong.lan> (raw)
In-Reply-To: <543CCC75.6070407@fultondesigns.co.uk> (William S. Fulton's message of "Tue, 14 Oct 2014 08:10:45 +0100")
William S Fulton <wsf@fultondesigns.co.uk> writes:
> Thanks for analysing and pointing in the right direction Mark. With
> this info I found
> https://github.com/ivmai/bdwgc/commit/8fc1f3b61b02320848b035ccccd59e04e77d3f6b#diff-b3f85dde7694cbd1268ea9ed20db1b1aR244
> which looks like it fixes it in the next release of bdwgc (7.5).
Thanks for letting us know. I'm closing this bug now.
Regards,
Mark
next prev parent reply other threads:[~2014-10-15 16:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-13 20:56 bug#18711: Numerous unknown attribute '__alloc_size__' warnings when using clang William S Fulton
2014-10-14 3:53 ` Mark H Weaver
2014-10-14 7:10 ` William S Fulton
2014-10-15 16:39 ` Mark H Weaver [this message]
2014-10-16 22:07 ` bug#18711: Re[2]: [Gc] " Ivan Maidanski
2014-10-14 10:09 ` Ludovic Courtès
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877g0170dh.fsf@yeeloong.lan \
--to=mhw@netris.org \
--cc=18711-done@debbugs.gnu.org \
--cc=wsf@fultondesigns.co.uk \
/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).