public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: c/2635
Date: Wed, 06 Jun 2001 00:46:00 -0000 [thread overview]
Message-ID: <20010606074602.31944.qmail@sourceware.cygnus.com> (raw)
The following reply was made to PR c/2635; it has been noted by GNATS.
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: Charlie Ross <rossc@cs.colostate.edu>
Cc: <gcc-gnats@gcc.gnu.org>
Subject: Re: c/2635
Date: Wed, 6 Jun 2001 08:37:07 +0100 (BST)
On Tue, 5 Jun 2001, Charlie Ross wrote:
> As described in the gnats report: a.c is the program which gives incorrect
> output when compiles with -O2 b.c is a program which generates more
> examples of a.c (a.c was created by running ./b > a.c
With whatever options I try, with 2.95.3 or with 3.0 branch, the program
produces the output
00001000 00001000 00001000 00001000
Can you test with 2.95.3 and see whether you can reproduce your problem?
--
Joseph S. Myers
jsm28@cam.ac.uk
next reply other threads:[~2001-06-06 0:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-06 0:46 Joseph S. Myers [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-06-05 19:36 c/2635 Charlie Ross
2001-06-05 14:26 c/2635 jsm28
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=20010606074602.31944.qmail@sourceware.cygnus.com \
--to=jsm28@cam.ac.uk \
--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).