public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libffi/46660] cls_double_va.c, cls_longdouble_va.c FAIL on IRIX 6.5
Date: Wed, 29 Jun 2011 13:40:00 -0000	[thread overview]
Message-ID: <bug-46660-4-OtGfjHUI6N@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46660-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46660

--- Comment #4 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> 2011-06-29 13:39:32 UTC ---
> This caused:
>
> FAIL: libffi.call/cls_double_va.c -O0 -W -Wall output pattern test, is 7.0
> FAIL: libffi.call/cls_double_va.c -O2 -fomit-frame-pointer output pattern test,
> is 7.0
> FAIL: libffi.call/cls_double_va.c -O2 output pattern test, is 7.0
> FAIL: libffi.call/cls_double_va.c -O3 output pattern test, is 7.0
> FAIL: libffi.call/cls_double_va.c -Os output pattern test, is 7.0
> FAIL: libffi.call/cls_longdouble_va.c -O0 -W -Wall output pattern test, is 7.0
> FAIL: libffi.call/cls_longdouble_va.c -O2 -fomit-frame-pointer output pattern
> test, is 7.0
> FAIL: libffi.call/cls_longdouble_va.c -O2 output pattern test, is 7.0
> FAIL: libffi.call/cls_longdouble_va.c -O3 output pattern test, is 7.0
> FAIL: libffi.call/cls_longdouble_va.c -Os output pattern test, is 7.0
>
> on Linux/x86.

Already fixed:

    http://gcc.gnu.org/ml/gcc-patches/2011-06/msg02227.html

    Rainer


  parent reply	other threads:[~2011-06-29 13:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-25 17:03 [Bug libffi/46660] New: " ro at gcc dot gnu.org
2011-06-29  7:31 ` [Bug libffi/46660] " ro at gcc dot gnu.org
2011-06-29  7:36 ` ro at gcc dot gnu.org
2011-06-29 13:39 ` hjl.tools at gmail dot com
2011-06-29 13:40 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message]
2011-07-19 14:53 ` ro at gcc dot gnu.org
2014-06-13 11:48 ` ro at gcc dot gnu.org

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-46660-4-OtGfjHUI6N@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).