public inbox for libffi-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Anthony Green <green@moxielogic.com>
To: Kiyoshi KANAZAWA <yoi_no_myoujou@yahoo.co.jp>
Cc: libffi-discuss <libffi-discuss@sourceware.org>
Subject: Re: [libffi-3.3] make check failes on Solaris 11.3 x64
Date: Sat, 23 Nov 2019 23:57:00 -0000	[thread overview]
Message-ID: <CACxje5-h6UbdPmdaB1qzp2yNR_HT07JfF_+GxL9iXfbWd1nV0w@mail.gmail.com> (raw)
In-Reply-To: <1752632687.3073736.1574550708042.JavaMail.yahoo@mail.yahoo.co.jp>

This is a gcc bug.  It is fixed in the newest version.

Thanks,

AG


On Sat., Nov. 23, 2019, 6:11 p.m. Kiyoshi KANAZAWA, <
yoi_no_myoujou@yahoo.co.jp> wrote:

> Hello,
>
> Trying to install libffi-3.3 on Solaris 11.3 x86/x64.
> Make check passed with 32 bits environment, but failed with 64 bits
> in new test feature "testsuite/libffi.bhaible/bhaible.exp".
>
>
> $ uname -a
> SunOS hidden 5.11 11.3 i86pc i386 i86pc
>
> $ gcc --version
> gcc (GCC) 7.5.0
>
>
> $ ./configure 'CC=gcc -m32'
>
> $ make
> $ make check
> passed.
>
>
> $ ./configure 'CC=gcc -m64'
>
> $ make
> $ make check
>   :
> Running target unix
> Using /opt/local/share/dejagnu/baseboards/unix.exp as board description
> file for target.
> Using /opt/local/share/dejagnu/config/unix.exp as generic interface file
> for target.
> Using ../../testsuite/config/default.exp as tool-and-target-specific
> interface file.
> Running ../../testsuite/libffi.bhaible/bhaible.exp ...
> FAIL: libffi.bhaible/test-call.c -W -Wall -Wno-psabi -DDGTEST=55
> -Wno-unused-variable -Wno-unused-parameter -Wno-unused-but-set-variable
> -Wno-uninitialized -O0 -DABI_NUM=FFI_GNUW64 -DABI_ATTR=__MSABI__ execution
> test
> FAIL: libffi.bhaible/test-call.c -W -Wall -Wno-psabi -DDGTEST=55
> -Wno-unused-variable -Wno-unused-parameter -Wno-unused-but-set-variable
> -Wno-uninitialized -O2 -DABI_NUM=FFI_GNUW64 -DABI_ATTR=__MSABI__ execution
> test
> FAIL: libffi.bhaible/test-call.c -W -Wall -Wno-psabi -DDGTEST=56
> -Wno-unused-variable -Wno-unused-parameter -Wno-unused-but-set-variable
> -Wno-uninitialized -O0 -DABI_NUM=FFI_GNUW64 -DABI_ATTR=__MSABI__ execution
> test
> FAIL: libffi.bhaible/test-call.c -W -Wall -Wno-psabi -DDGTEST=56
> -Wno-unused-variable -Wno-unused-parameter -Wno-unused-but-set-variable
> -Wno-uninitialized -O2 -DABI_NUM=FFI_GNUW64 -DABI_ATTR=__MSABI__ execution
> test
> FAIL: libffi.bhaible/test-call.c -W -Wall -Wno-psabi -DDGTEST=57
> -Wno-unused-variable -Wno-unused-parameter -Wno-unused-but-set-variable
> -Wno-uninitialized -O0 -DABI_NUM=FFI_GNUW64 -DABI_ATTR=__MSABI__ execution
> test
> FAIL: libffi.bhaible/test-call.c -W -Wall -Wno-psabi -DDGTEST=57
> -Wno-unused-variable -Wno-unused-parameter -Wno-unused-but-set-variable
> -Wno-uninitialized -O2 -DABI_NUM=FFI_GNUW64 -DABI_ATTR=__MSABI__ execution
> test
> FAIL: libffi.bhaible/test-callback.c -W -Wall -Wno-psabi -DDGTEST=54
> -Wno-unused-variable -Wno-unused-parameter -Wno-unused-but-set-variable
> -Wno-uninitialized -O0 -DABI_NUM=FFI_GNUW64 -DABI_ATTR=__MSABI__ execution
> test
> FAIL: libffi.bhaible/test-callback.c -W -Wall -Wno-psabi -DDGTEST=54
> -Wno-unused-variable -Wno-unused-parameter -Wno-unused-but-set-variable
> -Wno-uninitialized -O2 -DABI_NUM=FFI_GNUW64 -DABI_ATTR=__MSABI__ execution
> test
> FAIL: libffi.bhaible/test-callback.c -W -Wall -Wno-psabi -DDGTEST=55
> -Wno-unused-variable -Wno-unused-parameter -Wno-unused-but-set-variable
> -Wno-uninitialized -O0 -DABI_NUM=FFI_GNUW64 -DABI_ATTR=__MSABI__ execution
> test
> FAIL: libffi.bhaible/test-callback.c -W -Wall -Wno-psabi -DDGTEST=55
> -Wno-unused-variable -Wno-unused-parameter -Wno-unused-but-set-variable
> -Wno-uninitialized -O2 -DABI_NUM=FFI_GNUW64 -DABI_ATTR=__MSABI__ execution
> test
> FAIL: libffi.bhaible/test-callback.c -W -Wall -Wno-psabi -DDGTEST=56
> -Wno-unused-variable -Wno-unused-parameter -Wno-unused-but-set-variable
> -Wno-uninitialized -O0 -DABI_NUM=FFI_GNUW64 -DABI_ATTR=__MSABI__ execution
> test
> FAIL: libffi.bhaible/test-callback.c -W -Wall -Wno-psabi -DDGTEST=56
> -Wno-unused-variable -Wno-unused-parameter -Wno-unused-but-set-variable
> -Wno-uninitialized -O2 -DABI_NUM=FFI_GNUW64 -DABI_ATTR=__MSABI__ execution
> test
> Running ../../testsuite/libffi.call/call.exp ...
>   :
>
> Regards,
>
> --- Kiyoshi
>
>

      reply	other threads:[~2019-11-23 23:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1752632687.3073736.1574550708042.JavaMail.yahoo.ref@mail.yahoo.co.jp>
2019-11-23 23:11 ` Kiyoshi KANAZAWA
2019-11-23 23:57   ` Anthony Green [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=CACxje5-h6UbdPmdaB1qzp2yNR_HT07JfF_+GxL9iXfbWd1nV0w@mail.gmail.com \
    --to=green@moxielogic.com \
    --cc=libffi-discuss@sourceware.org \
    --cc=yoi_no_myoujou@yahoo.co.jp \
    /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).