public inbox for libffi-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Anthony Green <green@moxielogic.com>
To: James Greenhalgh <james.greenhalgh@arm.com>
Cc: "libffi-discuss\@sourceware.org" <libffi-discuss@sourceware.org>
Subject: Re: libffi 3.1-rc1 needs testing!
Date: Fri, 28 Mar 2014 17:33:00 -0000	[thread overview]
Message-ID: <8761my8bz1.fsf@moxielogic.com> (raw)
In-Reply-To: <20140328150533.GA31475@arm.com> (James Greenhalgh's message of	"Fri, 28 Mar 2014 15:05:34 +0000")

James Greenhalgh <james.greenhalgh@arm.com> writes:

> Hi,
>
> I'm seeing issues with libffi.call/float2.c on GCC 4.9 toolchains across
> ARM, AArch64, x86_64. I guess GCC 4.9 is more aggressive in warning for
> unused values:

Thanks James.  I just committed a fix for this.

AG




>
> FAIL: libffi.call/float2.c -W -Wall -O0 (test for excess errors)
> FAIL: libffi.call/float2.c -W -Wall -O2 (test for excess errors)
> FAIL: libffi.call/float2.c -W -Wall -O3 (test for excess errors)
> FAIL: libffi.call/float2.c -W -Wall -Os (test for excess errors)
> FAIL: libffi.call/float2.c -W -Wall -O2 -fomit-frame-pointer (test for excess errors)
>
> In file included from ../../testsuite/libffi.call/float2.c:10:0:
> ../../testsuite/libffi.call/float2.c: In function 'main':
> ../../testsuite/libffi.call/ffitest.h:18:39: warning: right-hand operand of comma expression has no effect [-Wunused-value]
>  #define CHECK(x) (!(x) ? (abort(), 1) : 0)
>                                        ^
> ../../testsuite/libffi.call/float2.c:55:5: note: in expansion of macro 'CHECK'
>      CHECK(0);
>      ^
> output is:
> In file included from ../../testsuite/libffi.call/float2.c:10:0:
> ../../testsuite/libffi.call/float2.c: In function 'main':
> ../../testsuite/libffi.call/ffitest.h:18:39: warning: right-hand operand of comma expression has no effect [-Wunused-value]
>  #define CHECK(x) (!(x) ? (abort(), 1) : 0)
>                                        ^
> ../../testsuite/libffi.call/float2.c:55:5: note: in expansion of macro 'CHECK'
>      CHECK(0);
>      ^
>
> Thanks,
> James

  reply	other threads:[~2014-03-28 17:33 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-01 23:49 libffi 3.0.14-rc0 " Anthony Green
2014-03-01 23:56 ` Anthony Green
2014-03-03 12:44 ` Dominik Vogt
2014-03-03 19:17 ` David Fang
2014-03-04  7:29 ` Will Newton
2014-03-05  0:31   ` Alan Hourihane
2014-03-04 22:14 ` Matthias Klose
2014-03-25 21:11 ` libffi 3.1-rc1 " Anthony Green
2014-03-27 12:23   ` Dominik Vogt
2014-03-27 12:25     ` Dominik Vogt
2014-03-27 12:31   ` Dominik Vogt
2014-03-27 12:40   ` Samuli Suominen
2014-03-27 12:45     ` Samuli Suominen
2014-03-27 12:55   ` Samuli Suominen
2014-03-28 15:43     ` Anthony Green
2014-03-28 15:05   ` James Greenhalgh
2014-03-28 17:33     ` Anthony Green [this message]
2014-04-24 12:47       ` Marcus Shawcroft
2014-03-28 20:37   ` Andreas Tobler
2014-03-28 20:39   ` Matthias Klose
2014-03-28 21:56     ` Anthony Green
2014-03-28 22:31       ` Anthony Green
2014-03-29 14:25     ` ABI breakage (Was: libffi 3.1-rc1 needs testing!) Anthony Green
2014-05-30 12:21       ` Matthias Klose

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=8761my8bz1.fsf@moxielogic.com \
    --to=green@moxielogic.com \
    --cc=james.greenhalgh@arm.com \
    --cc=libffi-discuss@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).