public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amylaar at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/39349] cse_insn has out-of-bounds array access
Date: Mon, 02 Mar 2009 18:30:00 -0000 [thread overview]
Message-ID: <20090302182953.26680.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39349-5394@http.gcc.gnu.org/bugzilla/>
------- Comment #2 from amylaar at gcc dot gnu dot org 2009-03-02 18:29 -------
(In reply to comment #1)
> I think this is by defined, you need to include one mode bigger than the
> register size. This is done for spu the same way.
Where does it say that a port for a target with 128 bit registers
and 8*16 bit ALU width has to support 256 bit integers?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39349
next prev parent reply other threads:[~2009-03-02 18:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-02 17:31 [Bug rtl-optimization/39349] New: " amylaar at gcc dot gnu dot org
2009-03-02 17:39 ` [Bug rtl-optimization/39349] " pinskia at gcc dot gnu dot org
2009-03-02 18:30 ` amylaar at gcc dot gnu dot org [this message]
2009-03-02 19:00 ` hjl dot tools at gmail dot com
2009-03-05 1:27 ` amylaar 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=20090302182953.26680.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).