public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Raimar Falke <rf13@inf.tu-dresden.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/8681: Generates unneeded test
Date: Mon, 02 Dec 2002 08:26:00 -0000	[thread overview]
Message-ID: <20021202162604.26789.qmail@sources.redhat.com> (raw)

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

From: Raimar Falke <rf13@inf.tu-dresden.de>
To: Christian Ehrhardt <ehrhardt@mathematik.uni-ulm.de>
Cc: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org,
   nobody@gcc.gnu.org
Subject: Re: c/8681: Generates unneeded test
Date: Mon, 2 Dec 2002 17:18:05 +0100

 On Mon, Dec 02, 2002 at 03:44:04PM +0100, Christian Ehrhardt wrote:
 > 
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8681
 
 > Did this ever work? It DOESN'T for me with: 2.95.2, 3.2, 3.2.1, 3.3.
 
 If you mean with "worked" that it had omitted the test in the past: I
 don't know. It is a new issue for me which I think gcc should
 optimize.
 
 I have also tested intel compiler 6.0 and 7.0 and both don't do the
 optimization. The sun compiler (Sun WorkShop 6 update 2 C 5.3) however
 will do the optimization if -depend is given.
 
 > This should be reclassified as change request. I can confirm that
 > the compiler doesn't do an optimization that looks valid to me.
 
 	Raimar
 
 -- 
  email: rf13@inf.tu-dresden.de
   The trick is to keep breathing.


             reply	other threads:[~2002-12-02 16:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-02  8:26 Raimar Falke [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-21 10:49 bangerth
2002-12-02  6:46 Christian Ehrhardt

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=20021202162604.26789.qmail@sources.redhat.com \
    --to=rf13@inf.tu-dresden.de \
    --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).