From: Richard Henderson <rth@twiddle.net>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL v2 00/18] target-alpha fpu improvements
Date: Fri, 22 May 2015 07:02:29 -0700 [thread overview]
Message-ID: <555F36F5.2080400@twiddle.net> (raw)
In-Reply-To: <CAFEAcA867c1GAKe9g-tQDq3Y1mkwL8cfpWUZ=rHVTeQLSUxA6Q@mail.gmail.com>
On 05/22/2015 04:32 AM, Peter Maydell wrote:
> On 22 May 2015 at 11:22, Peter Maydell <peter.maydell@linaro.org> wrote:
>> On 22 May 2015 at 11:00, Peter Maydell <peter.maydell@linaro.org> wrote:
>>> On 21 May 2015 at 18:39, Richard Henderson <rth@twiddle.net> wrote:
>>>> for you to fetch changes up to 32ad48abd74a997220b841e4e913edeb267aa362:
>>>>
>>>> target-alpha: Add vector implementation for CMPBGE (2015-05-21 10:34:18 -0700)
>>>
>>> Applied, thanks.
>>
>> Except I failed to notice a test failure from one of my builds
>> before pushing:
>>
>> target-alpha/int_helper.c: In function 'helper_cmpbge':
>> target-alpha/int_helper.c:77: error: invalid operands to binary >=
>> target-alpha/int_helper.c:79: error: subscripted value is neither
>> array nor pointer
>>
>> That's in the Centos5 build, which is
>> gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-55)
>>
>> Any suggestions?
>>
>> I do note that this build target is basically obsolete anyway, because
>> we're about to move to requiring glib 2.22, at which point Centos5 is
>> officially Too Old. So maybe we just say "yeah, you need a newer gcc" ?
>
> Hmm. This fails on some of the travis builds too, with slightly
> different warnings:
>
> gcc (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3
> target-alpha/int_helper.c:77:24: error: invalid operands to binary >=
> (have '__vector(16) unsigned char' and '__vector(16) unsigned char')
>
> I think the best thing to do for the moment is to revert commit
> 32ad48abd74a9 so we can get trunk building again, so I'm going to
> do that.
Wow, I would have thought 4.6 would have been new enough.
Sorry for the headache. Yes, a revert is probably best
until I can figure out what versions do what.
r~
prev parent reply other threads:[~2015-05-22 14:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 17:39 [Qemu-devel] [PULL v2 00/18] target-alpha fpu improvements Richard Henderson
2015-05-21 17:39 ` [Qemu-devel] [PULL v2 17/18] target-alpha: Rewrite helper_zapnot Richard Henderson
2015-05-21 20:08 ` [Qemu-devel] [PULL v2 00/18] target-alpha fpu improvements Peter Maydell
2015-05-21 20:10 ` Richard Henderson
2015-05-22 10:00 ` Peter Maydell
2015-05-22 10:22 ` Peter Maydell
2015-05-22 11:32 ` Peter Maydell
2015-05-22 14:02 ` Richard Henderson [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=555F36F5.2080400@twiddle.net \
--to=rth@twiddle.net \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).