public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "uros at kss-loka dot si" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/23831] [4.1 Regression] ICE in immed_double_const with vectorized multipication
Date: Thu, 15 Sep 2005 11:53:00 -0000 [thread overview]
Message-ID: <20050915115351.16594.qmail@sourceware.org> (raw)
In-Reply-To: <20050912091729.23831.uros@kss-loka.si>
------- Additional Comments From uros at kss-loka dot si 2005-09-15 11:53 -------
He problem is in following RTL:
(insn 30 29 31 1 (set (reg:V4SI 75)
(mem/u/i:V4SI (symbol_ref/u:SI ("*.LC0") [flags 0x2]) [3 S16 A128]))
541 {*movv4si_internal} (nil)
(expr_list:REG_EQUAL (const_vector:V4SI [
(const_int 5 [0x5])
(const_int 5 [0x5])
(const_int 5 [0x5])
(const_int 5 [0x5])
])
(nil)))
...
(insn 33 32 34 1 (set (subreg:TI (reg:V4SI 78) 0)
(lshiftrt:TI (subreg:TI (reg:V4SI 75) 0)
(const_int 32 [0x20]))) 709 {sse2_lshrti3} (nil)
(nil))
Somehow a TImode constant is produced, and it triggers the check below:
gcc_assert (GET_MODE_CLASS (mode) == MODE_INT
|| GET_MODE_CLASS (mode) == MODE_PARTIAL_INT
/* We can get a 0 for an error mark. */
|| GET_MODE_CLASS (mode) == MODE_VECTOR_INT
|| GET_MODE_CLASS (mode) == MODE_VECTOR_FLOAT);
/* We clear out all bits that don't belong in MODE, unless they and
our sign bit are all one. So we get either a reasonable negative
value or a reasonable unsigned value for this mode. */
width = GET_MODE_BITSIZE (mode);
if (width < HOST_BITS_PER_WIDE_INT
&& ((i0 & ((HOST_WIDE_INT) (-1) << (width - 1)))
!= ((HOST_WIDE_INT) (-1) << (width - 1))))
i0 &= ((HOST_WIDE_INT) 1 << width) - 1, i1 = 0;
else if (width == HOST_BITS_PER_WIDE_INT
&& ! (i1 == ~0 && i0 < 0))
i1 = 0;
else
/* We should be able to represent this value as a constant. */
>>> gcc_assert (width <= 2 * HOST_BITS_PER_WIDE_INT);
HOSTS_BITS_PER_WIDE_INT is 32 bit for ia32, and TImode constants are 128 bit
wide. I don't know the correct solution here. If the assert is commented out,
the ICE goes away and produced code works as expected.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23831
next prev parent reply other threads:[~2005-09-15 11:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-12 9:17 [Bug target/23831] New: " uros at kss-loka dot si
2005-09-12 13:51 ` [Bug target/23831] [4.1 Regression] " pinskia at gcc dot gnu dot org
2005-09-15 11:53 ` uros at kss-loka dot si [this message]
2005-09-15 14:48 ` pinskia at gcc dot gnu dot org
2005-09-15 14:54 ` pinskia at gcc dot gnu dot org
2005-09-26 8:59 ` [Bug middle-end/23831] " uros at kss-loka dot si
2005-09-26 18:16 ` cvs-commit at gcc dot gnu dot org
2005-09-26 18:18 ` cvs-commit at gcc dot gnu dot org
2005-09-26 19:55 ` pinskia 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=20050915115351.16594.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).