public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Janis Johnson <janis187@us.ibm.com>
To: jakub@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: middle-end/5877: negative offset to array index leads to inefficient code
Date: Mon, 11 Mar 2002 08:46:00 -0000	[thread overview]
Message-ID: <20020311164601.16770.qmail@sources.redhat.com> (raw)

The following reply was made to PR middle-end/5877; it has been noted by GNATS.

From: Janis Johnson <janis187@us.ibm.com>
To: rodrigc@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
        jakub@gcc.gnu.org, janis187@us.ibm.com, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: middle-end/5877: negative offset to array index leads to inefficient code
Date: Mon, 11 Mar 2002 08:49:41 -0800

 On Sun, Mar 10, 2002 at 07:13:56PM -0000, rodrigc@gcc.gnu.org wrote:
 > Synopsis: negative offset to array index leads to inefficient code
 > 
 > State-Changed-From-To: open->feedback
 > State-Changed-By: rodrigc
 > State-Changed-When: Sun Mar 10 11:13:56 2002
 > State-Changed-Why:
 >     Can you verify if this solves the problem?
 >     
 >     
 >     
 >     2002-03-09  Jakub Jelinek  <jakub@redhat.com>
 >      
 >             PR middle-end/5877
 >             * expr.c (highest_pow2_factor): Check TREE_INT_CST_LOW
 >             even for non-representable constants.
 > 
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5877
 
 Yes, it does.  Thanks, Jakub!
 
 Janis


             reply	other threads:[~2002-03-11 16:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-11  8:46 Janis Johnson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-11  9:19 rodrigc
2002-03-10 11:13 rodrigc
2002-03-08 10:11 jakub
2002-03-07 16:06 janis187

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=20020311164601.16770.qmail@sources.redhat.com \
    --to=janis187@us.ibm.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=jakub@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).