unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: William S Fulton <wsf@fultondesigns.co.uk>
To: Mark H Weaver <mhw@netris.org>
Cc: bdwgc@lists.opendylan.org, 18711@debbugs.gnu.org
Subject: bug#18711: Numerous unknown attribute '__alloc_size__' warnings when using clang
Date: Tue, 14 Oct 2014 08:10:45 +0100	[thread overview]
Message-ID: <543CCC75.6070407@fultondesigns.co.uk> (raw)
In-Reply-To: <871tqbgvca.fsf@yeeloong.lan>

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).

Unfortunately this warning fails our tests as the build log is too big 
(this warning leads to > 4GByte build logs as the header is used in 
hundreds of our tests), so I'll suppress it some other way until 7.5 is 
released.

William

On 14/10/14 04:53, Mark H Weaver wrote:
> [Forwarding this bug report to bdwgc@lists.opendylan.org]
>
> William S Fulton <wsf@fultondesigns.co.uk> writes:
>
>> A simple
>>
>> #include <libguile.h>
>>
>> generates the numerous warnings given below:
>>
>>
>> In file included from example_wrap.c:702:
>> In file included from /usr/local/Cellar/guile/2.0.11_1/include/guile/2.0/libguile.h:37:
>> In file included from /usr/local/Cellar/guile/2.0.11_1/include/guile/2.0/libguile/async.h:28:
>> In file included from /usr/local/Cellar/guile/2.0.11_1/include/guile/2.0/libguile/threads.h:36:
>> In file included from /usr/local/Cellar/guile/2.0.11_1/include/guile/2.0/libguile/pthread-threads.h:33:
>> In file included from /usr/local/Cellar/guile/2.0.11_1/include/guile/2.0/libguile/bdw-gc.h:47:
>> /usr/local/Cellar/bdw-gc/7.4.2/include/gc/gc.h:411:23: warning: unknown attribute '__alloc_size__' ignored [-Wattributes]
>> GC_API GC_ATTR_MALLOC GC_ATTR_ALLOC_SIZE(1) void * GC_CALL
>> ^
>> /usr/local/Cellar/bdw-gc/7.4.2/include/gc/gc_config_macros.h:249:54: note: expanded from macro 'GC_ATTR_ALLOC_SIZE'
>> # define GC_ATTR_ALLOC_SIZE(argnum) __attribute__((__alloc_size__(argnum)))
>> ^
> This is clearly an issue with bdwgc on clang, and possibly only on
> Apple's version of clang.  Here's the relevant section of
> gc/gc_config_macros.h from bdwgc 7.4.2:
>
> --8<---------------cut here---------------start------------->8---
> #ifndef GC_ATTR_ALLOC_SIZE
>    /* 'alloc_size' attribute improves __builtin_object_size correctness. */
>    /* Only single-argument form of 'alloc_size' attribute is used.       */
> # if defined(__GNUC__) && (__GNUC__ > 4 \
>          || (__GNUC__ == 4 && __GNUC_MINOR__ >= 3 && !defined(__ICC)) \
>          || __clang_major__ > 3 \
>          || (__clang_major__ == 3 && __clang_minor__ >= 2))
> #   define GC_ATTR_ALLOC_SIZE(argnum) __attribute__((__alloc_size__(argnum)))
> # else
> #   define GC_ATTR_ALLOC_SIZE(argnum)
> # endif
> #endif
> --8<---------------cut here---------------end--------------->8---
>
> You can see that the bdwgc developers have made an effort to check both
> GCC and clang version numbers before using the __alloc_size__ attribute.
> The code above seems to suggest that they believed clang 3.2 or later
> supported this attribute, whereas your version of clang seems to be
> based on upstream clang 3.5.  Perhaps Apple removed support for this
> attribute from their clang?
>
> In any case, this needs to be taken up with the bdwgc developers.
>
>      Regards,
>        Mark
>
>
>> System information:
>>
>> $ guile --version | head -n 1
>> guile (GNU Guile) 2.0.11
>>
>> $ clang --version
>> Apple LLVM version 6.0 (clang-600.0.51) (based on LLVM 3.5svn)
>> Target: x86_64-apple-darwin13.4.0
>> Thread model: posix
>>
>> $ xcodebuild -version -sdk | head -n 2
>> MacOSX10.9.sdk - OS X 10.9 (macosx10.9)
>> SDKVersion: 10.9
>>
>> $ sw_vers
>> ProductName: Mac OS X
>> ProductVersion: 10.9.5
>> BuildVersion: 13F34
>>
>> $ uname -a
>> Darwin itako16071.miso 13.4.0 Darwin Kernel Version 13.4.0: Sun Aug 17
>> 19:50:11 PDT 2014; root:xnu-2422.115.4~1/RELEASE_X86_64 x86_64






  reply	other threads:[~2014-10-14  7:10 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 [this message]
2014-10-15 16:39     ` Mark H Weaver
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=543CCC75.6070407@fultondesigns.co.uk \
    --to=wsf@fultondesigns.co.uk \
    --cc=18711@debbugs.gnu.org \
    --cc=bdwgc@lists.opendylan.org \
    --cc=mhw@netris.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).