public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Berger David-MGI2063 <dberger@motorola.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: RE: optimization/10362: Optimization with constant shifts and com pares fails on MIPS and x86 - probably all
Date: Wed, 09 Apr 2003 19:26:00 -0000	[thread overview]
Message-ID: <20030409192600.17213.qmail@sources.redhat.com> (raw)

The following reply was made to PR optimization/10362; it has been noted by GNATS.

From: Berger David-MGI2063 <dberger@motorola.com>
To: "'gcc-gnats@gcc.gnu.org'" <gcc-gnats@gcc.gnu.org>
Cc:  
Subject: RE: optimization/10362: Optimization with constant shifts and com
	pares fails on MIPS and x86 - probably all
Date: Wed, 9 Apr 2003 12:19:25 -0700 

 I'd like to admend this bug report: it does the same thing on the x86 as well, which indicates it is a front-end bug.  David.
 
 -----Original Message-----
 From: gcc-gnats@gcc.gnu.org [mailto:gcc-gnats@gcc.gnu.org] 
 Sent: Wednesday, April 09, 2003 11:46 AM
 To: David Berger
 Subject: Re: optimization/10362: Optimization with constant shifts and compares fails on MIPS
 
 
 Thank you very much for your problem report.
 It has the internal identification `optimization/10362'.
 The individual assigned to look at your
 report is: unassigned. 
 
 >Category:       optimization
 >Responsible:    unassigned
 >Synopsis:       Optimization with constant shifts and compares fails on MIPS
 >Arrival-Date:   Wed Apr 09 18:46:00 UTC 2003


             reply	other threads:[~2003-04-09 19:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-09 19:26 Berger David-MGI2063 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-09 19:26 Berger David-MGI2063

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=20030409192600.17213.qmail@sources.redhat.com \
    --to=dberger@motorola.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).