Re: Uninitialized use warning message

Kean Johnston wrote: >> A common situation would be: >> >> if (condition) { >> flag = 1 >> msg = "Hello World"; >> } else >> flag = 0;[1] >> ... >> if (flag) >> printf ("I say, %s\n", msg);[2] >> >> Point [1] is where I "fail" to init

help: about enum

Hi, Plz help me I want to know, how enums are handled in gcc. How do we map an enum value to the corresponding integer size. What does the option -fshort-enums does. Plz explain me in detail. I could see the difference in the size of enums when I toggle the option. If the option is not given,

Problem building 3.3.6 (with 3.4.4): xgcc: cannot specify -o with -c or -S and multiple compilations

Can anybody explain what this error might mean? /tmp/gcc-3-3.heretix/work/gcc/xgcc "" -B/tmp/gcc-3-3.heretix/work/gcc/ -nostdinc++ -L/tmp/gcc-3-3.heretix/work/x86_64-unknown-linux-gnu/libstdc++-v3/src -L/tmp/gcc-3-3.heretix/work/x86 _64-unknown-linux-gnu/libstdc++-v3/src/.libs -B/pkg/gcc-3-3/x

RE: help: about enum

Hi, I am sorry, I wrote incorrectly in the earlier mail. That "I could see the difference in the size of enums when I toggle the option. If the option is not given, then all the enum occupy the same 4 bytes irrespective of their value and 2147483647 is the maximum value that can fit in integer.

Re: Uninitialized use warning message

Kean Johnston <[EMAIL PROTECTED]> writes: >> A common situation would be: >> if (condition) { >> flag = 1 >> msg = "Hello World"; >> } else >> flag = 0; [1] >> ... >> if (flag) >> printf ("I say, %s\n", m

Re: Uninitialized use warning message

program that is completely unrealistic. However, warning at 2 should be trivial. Unfortunately, it isn't. This warning happens very late in the processing, after a lot of mangling has been done. Take: I really mean't to sat trivial by comparison :) The point you raise about all the mangling a

Re: Incoming Message

Your file is attached.

Re: 4.2 Project: "@file" support

On Aug 25, 2005, DJ Delorie <[EMAIL PROTECTED]> wrote: > If "@string" is seen, but "string" does not represent an existing > file, the string "@string" is passed to the program as-is. With the terrible side effect of letting people think their applications will just work, but introducing the very

Re: Need help creating a small test case for g++ 4.0.0 bug

Hi Dan, Reply below. Best regards On Thu, 4 Aug 2005 02:05, Dan Kegel wrote: > "Paul C. Leopardi" <[EMAIL PROTECTED]> wrote: > > So I seem to be left with a large ( >2.5MB ) preprocessed source file. > > Should I try to report the bug using this large file as a test case? > > Sure. But you might

Re: Redundant limit check for switch

I know nothing about GCC internals, but it appears that it knows which bits are used in expressions: unsigned char foo(int x) { return (x + 1) & 0x0f & 0x0c & 0x3ff; } .file "test.c" .section .text .p2align 4,,15 .globl _foo _foo: pushl %ebp movl %esp, %ebp movb 8(%ebp), %al popl %ebp in