public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/38697] gcc.target/arm/neon/neon.exp tests for vmov fail on arm-linux-eabi
Date: Wed, 11 Mar 2009 22:43:00 -0000 [thread overview]
Message-ID: <20090311224329.22507.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38697-7210@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from joseph at codesourcery dot com 2009-03-11 22:43 -------
Subject: Re: gcc.target/arm/neon/neon.exp tests for vmov
fail on arm-linux-eabi
On Wed, 11 Mar 2009, jules at gcc dot gnu dot org wrote:
> These failures show up because the tests are kind of weak. There's no
> particular reason that vget_low* intrinsics should generate vmov instructions
> as the tests are expecting: the assembly output shown with vldr/fstd works just
> as well, and no instructions at all (i.e. just a hint to the register
> allocator) would work even better.
That's the move intrinsic tests. I think polytypes.c is because of
additional diagnostics added at some point for which target-independent
tests were updated but not all target-specific tests (i.e., the testcase
needs updating for the current front-end diagnostics). Unlike the move
instrinsics tests polytypes.c is not an automatically generated file, so
should be straightforward for anyone to fix.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38697
next prev parent reply other threads:[~2009-03-11 22:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-02 13:44 [Bug target/38697] New: " laurent at guerby dot net
2009-01-02 13:45 ` [Bug target/38697] " laurent at guerby dot net
2009-02-03 20:53 ` danglin at gcc dot gnu dot org
2009-03-11 20:47 ` jules at gcc dot gnu dot org
2009-03-11 22:43 ` joseph at codesourcery dot com [this message]
2009-03-11 22:58 ` laurent at guerby dot net
2009-12-08 22:42 ` laurent at guerby dot net
2010-01-09 16:48 ` ramana at gcc dot gnu dot org
2010-01-19 14:21 ` ramana at gcc dot gnu dot org
2010-01-25 12:29 ` ramana at gcc dot gnu dot org
2010-01-25 12:31 ` ramana at gcc dot gnu dot 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=20090311224329.22507.qmail@sourceware.org \
--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).