From: John Richard Moser <nigelenki@comcast.net>
To: Jim Wilson <wilson@specifixinc.com>
Cc: Denis Zaitsev <zzz@anda.ru>, linux-gcc@vger.kernel.org, gcc@gcc.gnu.org
Subject: Re: GCC 3.3.2 -Wall affects the code generated...
Date: Tue, 06 Jul 2004 17:11:34 -0400 [thread overview]
Message-ID: <40EB1586.4080307@comcast.net> (raw)
In-Reply-To: <40EB0E5E.4020002@specifixinc.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jim Wilson wrote:
| Denis Zaitsev wrote:
|
| know of any other reason why -Wall would effect the code emitted.
AFFECT
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFA6xWEhDd4aOud5P8RAgDkAJ94vibaOqcTaSaLawg8LfCFBNqSjwCePPuC
iZEYFTr8NWdZ4zHy6AT+djs=
=qTaC
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-07-06 21:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-01 18:03 GCC 3.3.2 -Wall affects the code generated Denis Zaitsev
2004-07-06 20:41 ` Jim Wilson
2004-07-06 21:11 ` John Richard Moser [this message]
2004-07-06 22:46 ` Denis Zaitsev
2004-07-07 0:20 ` Jim Wilson
2004-07-07 7:44 ` Denis Zaitsev
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=40EB1586.4080307@comcast.net \
--to=nigelenki@comcast.net \
--cc=gcc@gcc.gnu.org \
--cc=linux-gcc@vger.kernel.org \
--cc=wilson@specifixinc.com \
--cc=zzz@anda.ru \
/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 NNTP newsgroup(s).