public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rth at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug optimization/13772] [tree-ssa] ICE in get_expr_operands
Date: Thu, 22 Jan 2004 19:45:00 -0000	[thread overview]
Message-ID: <20040122194536.14405.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040120162056.13772.reichelt@gcc.gnu.org>


------- Additional Comments From rth at redhat dot com  2004-01-22 19:45 -------
Subject: Re: PR 13772 candidate fix

On Thu, Jan 22, 2004 at 02:07:12PM +0100, Andreas Schwab wrote:
> (mem/s:TI (post_modify:DI (reg/f:DI 36 loc4 [400])
>         (plus:DI (reg/f:DI 36 loc4 [400])
>             (const_int 8 [0x8]))) [4 opt__R47s+0 S16 A128])

Yep, looking at the patch, I was about to remind Zack that 
(1) post-modify can take registers as well as constants, and
(2) you have to check for overflowing the 9-bit post-modify
    constant.

Hum, and, actually, that post-modify seems very improbable.
addr += addr?  There's sure to be a typo somewhere.


r~


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13772


  parent reply	other threads:[~2004-01-22 19:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-20 16:20 [Bug c++/13772] New: " reichelt at gcc dot gnu dot org
2004-01-20 16:25 ` [Bug optimization/13772] " pinskia at gcc dot gnu dot org
2004-01-22 10:41 ` zack at codesourcery dot com
2004-01-22 11:02 ` zack at codesourcery dot com
2004-01-22 13:07 ` schwab at suse dot de
2004-01-22 16:06 ` bangerth at dealii dot org
2004-01-22 19:45 ` rth at redhat dot com [this message]
2004-01-23 14:51 ` reichelt 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=20040122194536.14405.qmail@sources.redhat.com \
    --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).