From: kamelopardus <killorn@yandex.ru>
To: gcc-help@gcc.gnu.org
Subject: gcc warnings
Date: Tue, 12 Aug 2008 15:36:00 -0000 [thread overview]
Message-ID: <18946614.post@talk.nabble.com> (raw)
Hello.
I use gcc 3.4.2 under mingw32. I need to put compiler warnings about
uninitialized variables into some text file, for example, "warnings.txt".
i try
gcc -O -Wuninitialized -v echo.c>warnings.txt
after the execution i can see warnings on the screen, but file
"warnings.txt" is empty.
Can anyone advise, where am i wrong?
--
View this message in context: http://www.nabble.com/gcc-warnings-tp18946614p18946614.html
Sent from the gcc - Help mailing list archive at Nabble.com.
next reply other threads:[~2008-08-12 15:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-12 15:36 kamelopardus [this message]
2008-08-12 15:48 ` Andrew Bell
2008-08-12 15:52 ` Joel Dice
2008-08-12 17:19 ` kamelopardus
-- strict thread matches above, loose matches on Subject: below --
2007-10-17 9:08 Humpolicek, Jiri - Acision
2007-10-17 11:48 ` John Love-Jensen
2007-10-17 11:49 ` Tom St Denis
2007-10-17 14:08 ` Humpolicek, Jiri - Acision
2007-10-17 13:28 ` Tim Prince
2007-10-17 14:28 ` Humpolicek, Jiri - Acision
2007-10-17 15:25 ` Andrew Haley
2000-05-24 14:29 Zia Babar
2000-05-24 23:48 ` Martin v. Loewis
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=18946614.post@talk.nabble.com \
--to=killorn@yandex.ru \
--cc=gcc-help@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).