public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/94603] ICE: in extract_insn, at recog.c:2343 (unrecognizable insn) with -mno-sse2 and __builtin_ia32_movq128
Date: Wed, 15 Apr 2020 08:38:50 +0000 [thread overview]
Message-ID: <bug-94603-4-iTZSzplQgY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94603-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94603
--- Comment #6 from Uroš Bizjak <ubizjak at gmail dot com> ---
(In reply to Jakub Jelinek from comment #5)
> (In reply to Uroš Bizjak from comment #4)
> > (In reply to Jakub Jelinek from comment #3)
> > > The testcase will need -msse -mno-sse2.
> >
> > Yes, but the testcase is invalid, because __builtin_ia32_movq128 should not
> > be used without SSE2. Fixed compiler reports:
> >
> > pr94603.c: In function ‘foo’:
> > pr94603.c:6:10: warning: implicit declaration of function
> > ‘__builtin_ia32_movq128’; did you mean ‘__builtin_ia32_movntps’?
> > [-Wimplicit-function-declaration]
> > pr94603.c:6:10: error: incompatible types when returning type ‘int’ but ‘V’
> > {aka ‘__vector(2) long long int’} was expected
>
> I know. But we (often) include even invalid testcases, perhaps with just
> dg-error "" and dg-warning "" (or use -w too) if we don't care about exact
> wording but just want to verify there is no ICE.
This is the testcase:
--cut here--
/* PR target/94603 */
/* { dg-do compile } */
/* { dg-options "-Wno-implicit-function-declaration -msse -mno-sse2" } */
typedef long long __attribute__ ((__vector_size__ (16))) V;
V
foo (V v)
{
return __builtin_ia32_movq128 (v); /* { dg-error "" } */
}
--cut here--
next prev parent reply other threads:[~2020-04-15 8:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 7:02 [Bug target/94603] New: " zsojka at seznam dot cz
2020-04-15 7:27 ` [Bug target/94603] " marxin at gcc dot gnu.org
2020-04-15 7:57 ` ubizjak at gmail dot com
2020-04-15 8:16 ` jakub at gcc dot gnu.org
2020-04-15 8:22 ` ubizjak at gmail dot com
2020-04-15 8:25 ` jakub at gcc dot gnu.org
2020-04-15 8:38 ` ubizjak at gmail dot com [this message]
2020-04-15 15:08 ` cvs-commit at gcc dot gnu.org
2020-04-15 20:03 ` cvs-commit at gcc dot gnu.org
2020-04-15 21:26 ` cvs-commit at gcc dot gnu.org
2020-04-15 21:27 ` ubizjak at gmail dot com
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-94603-4-iTZSzplQgY@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).