public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/4130: gcc 3.0 -O2 and printf optimization
Date: Wed, 03 Apr 2002 10:26:00 -0000	[thread overview]
Message-ID: <20020403182601.3072.qmail@sources.redhat.com> (raw)

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

From: Richard Henderson <rth@redhat.com>
To: Richard Kettlewell <rjk@greenend.org.uk>
Cc: gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Subject: Re: optimization/4130: gcc 3.0 -O2 and printf optimization
Date: Wed, 3 Apr 2002 10:23:13 -0800

 ----- Forwarded message from "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu> -----
 
 In addition, the builtin printf optimization (really all stdio
 builtins) are not performed if the return value is examined.  This is
 specifically to address the particular problem of how these functions
 all differently handle return values and errno.  So if you're actually
 going to examine errno, you should do it as I've done below.  (Code
 rewritten from the example provided in the PR):
 
  > #include <stdio.h>
  > #include <errno.h>
  > int main(void)
  > {
  >   if (printf ("foo\xC0\n") < 0)
  >     perror("printf");
  >   return 0;
  > }
 
 or something similar.  In this case, the optimization to `puts' is not
 done.


             reply	other threads:[~2002-04-03 18:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-03 10:26 Richard Henderson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-03 10:46 Richard Henderson
2002-04-03  2:36 Richard Kettlewell
2002-04-03  0:20 rth
2001-08-26  3:36 Richard Kettlewell

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=20020403182601.3072.qmail@sources.redhat.com \
    --to=rth@redhat.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).