public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/10339: strncmp generates imPure code (fwd)
Date: Mon, 07 Apr 2003 18:46:00 -0000	[thread overview]
Message-ID: <20030407184602.13963.qmail@sources.redhat.com> (raw)

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

From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: c/10339: strncmp generates imPure code (fwd)
Date: Mon, 7 Apr 2003 13:41:28 -0500 (CDT)

 ---------- Forwarded message ----------
 Date: Mon, 07 Apr 2003 11:19:33 -0700
 From: Michael Ubell <ubell@mindspring.com>
 To: Wolfgang Bangerth <bangerth@ices.utexas.edu>
 Subject: Re: c/10339: strncmp generates imPure code
 
 I am sorry for the tersness.  I guess I have been looking at the generated code 
 too much so that it becomes obvious to me.  Yes that is exactly the problem.
 
 Note that in this case the compiler could actually figure out the
 maximum number of bytes, but in a more general case (the original problem
 we saw under Purify) it cannot.
 


                 reply	other threads:[~2003-04-07 18:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030407184602.13963.qmail@sources.redhat.com \
    --to=bangerth@ices.utexas.edu \
    --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).