From: Jeff King <peff@peff.net>
To: Stefan Beller <sbeller@google.com>
Cc: Eric Sunshine <sunshine@sunshineco.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: test suite failure t5570, 8 with v2.4.1-168-g1ea28e1
Date: Tue, 19 May 2015 23:01:18 -0400 [thread overview]
Message-ID: <20150520030118.GA7223@peff.net> (raw)
In-Reply-To: <CAGZ79kbHVeNPQr_A3izp41WLRcaroHfN6NJObWcURQk4B=NYWA@mail.gmail.com>
On Tue, May 19, 2015 at 12:16:57PM -0700, Stefan Beller wrote:
> I did have a special flag set, which is
> CC = /usr/lib/gcc-snapshot/bin/gcc
> which is using the latest snapshot of the gcc compiler
> gcc (Ubuntu 20140405-0ubuntu1) 4.9.0 20140405
> (experimental) [trunk revision 209146]
I'm not sure 2014 counts as the "latest". :) My stock compiler is 4.9.2,
and gcc-snapshot on Debian unstable is:
gcc (Debian 20150516-1) 6.0.0 20150516 (experimental)
[trunk revision 223239]
> Could somebody try to reproduce the failing test using the latest gcc
> snapshot compiler?
Both versions I listed above seem to work fine for me. Of course we
can't definitively rule out git provoking undefined behavior in certain
compiler versions, but short of more data, I'd say it's probably a gcc
bug in 4.9.0 which has since been fixed.
-Peff
prev parent reply other threads:[~2015-05-20 3:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 17:20 test suite failure t5570, 8 with v2.4.1-168-g1ea28e1 Stefan Beller
2015-05-19 17:22 ` Stefan Beller
2015-05-19 17:22 ` Jeff King
2015-05-19 17:24 ` Stefan Beller
2015-05-19 17:31 ` Stefan Beller
2015-05-19 17:34 ` Stefan Beller
2015-05-19 17:53 ` Stefan Beller
2015-05-19 19:16 ` Stefan Beller
2015-05-20 3:01 ` Jeff King [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=20150520030118.GA7223@peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=sbeller@google.com \
--cc=sunshine@sunshineco.com \
/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 NNTP newsgroup(s).