public inbox for libffi-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Dominik Vogt <vogt@linux.vnet.ibm.com>
To: libffi-discuss@sourceware.org
Subject: Re: libffi 3.1-rc1 needs testing!
Date: Thu, 27 Mar 2014 12:25:00 -0000	[thread overview]
Message-ID: <20140327122527.GA9909@linux.vnet.ibm.com> (raw)
In-Reply-To: <20140327122310.GA9345@linux.vnet.ibm.com>

On Thu, Mar 27, 2014 at 01:23:10PM +0100, Dominik Vogt wrote:
> Host: s390x-unknown-linux-gnu
Ups:          ^^^^^^^
              ibm
> Toolchain: gcc-4.8.3 20140221 (prerelease), binutils-2.23.52.20130314
> Failures: 0
> 
> Host: s390-unknown-linux-gnu
             ^^^^^^^
             ibm
> Toolchain: gcc-4.7.2 20120921, binutils-2.22.52.0.1-10.fc17 2012013
> Failures: 0

Ciao

Dominik ^_^  ^_^

-- 

Dominik Vogt
IBM Germany

  reply	other threads:[~2014-03-27 12:25 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 [this message]
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
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=20140327122527.GA9909@linux.vnet.ibm.com \
    --to=vogt@linux.vnet.ibm.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).