On Wed, Sep 4, 2013 at 8:07 AM, Umesh Kalappa wrote:
> Hi Ian,
> For the below case, when I compile with O3 on X86.Gcc 4.6.3 emits asm with
> ret 1.
>
> Which I feel incorrect.
When p == 0 the program has undefined behaviour, so there is no
incorrect result in that case. When p != 0 the function
On Wed, Sep 4, 2013 at 6:40 AM, Kirill Tkhai wrote:
>
> the following example compiles without warnings:
>
> $ cat a.c
> int func (int p)
> {
> int x;
> if (p != 0)
> x = 1;
> return x;
> }
>
> $ gcc -c a.c -Wall
> (no messages)
>
> Is there no error? Why co
http://gcc.gnu.org/wiki/FunctionMultiVersioning says "This support has been
checked in to trunk and should be available when GCC 4.8 is released."
Since 4.8 has been released, and lists multiversioning support in the release
notes, should the page be updated to reflect this?
-Kenny
Hi,
the following example compiles without warnings:
$ cat a.c
int func (int p)
{
int x;
if (p != 0)
x = 1;
return x;
}
$ gcc -c a.c -Wall
(no messages)
Is there no error? Why compiler doesn't print a error
about uninitialized variable?
I saw many pieces
On Tue, Sep 3, 2013 at 7:59 PM, wrote:
> Sorry forgot to mention, my name is Tuncer.
>
> Again any help would be much appreciated.
> I know these maybe simple for some of you if you could lend me a hand, you
> will be doing a great deal of help.
>
> Changed the subject for better understanding,
>
