[EMAIL PROTECTED] said:
> Or these messages should going (by an option) to the stdout rather than
> stderr, so i can write a parser (gcc a.c | myparser) to convert the
> messages.
Ah, but that option does exist already:
gcc a.c 2>&1 | myparser
:-)
Christi
Hi all,
I am somewhat confused about the status of the
"may be used uninitialized" warning...
Consider:
--- testit.c ---
#include
static void
testit(int *a, int cnt)
{
struct {int score; int d;} best;
int i;
best.score = 0;
for (i = 0; i < cnt; i++)
if (a[i] > best.score) {
b
Ok, a slightly simpler testcase still shows the warning:
--- testit.c ---
#include
static void
testit(unsigned int *a, unsigned int cnt)
{
struct {unsigned int score; unsigned int d;} best;
unsigned int i;
best.score = 0;
for (i = 0; i < cnt; i++)
if (a[i] > best.score) {
best.
[EMAIL PROTECTED] said:
> Sub-optimal?
Yes, there is one more instruction to set the variable to 0...
--- testit_1.s 2006-01-12 16:38:06.13376 +0100
+++ testit.s2006-01-12 16:57:04.844986000 +0100
@@ -16,6 +16,7 @@
testl %ebx, %ebx
je .L9
movl$0, %edx
On Wed, 9 Aug 2006 09:09:56 -0700, Bruce Korb wrote:
> const char * pOptTitle;
const char * pOptTitle = pOptTitle;
is another possibility to shut the warning... without adding any
generated code...
There was another discussion about this issue here:
http://gcc.gnu.org/ml/gcc/2006-01/msg00274
Hi,
[EMAIL PROTECTED] said:
> I believe we'd need at least the source code of this function to be
> able to duplicate the problem with GCC. Would you please submit a
> full bug report, following the guidelines at http://gcc.gnu.org/
> bugs.html>? Thanks in advance,
Ok, I filed a bug report to
