GSoC project

2021-02-21 Thread Utkarsh singh via Gcc
Greeting to the team,
I  am Utkarsh Singh. I was going through various projects in the
archive section of GSoC. I searched for some specific projects in
Mathematics and C programming as I am most used with this field. I feel I
can contribute to the organisation which is in turn contributing to the
world. I wanted to know if the organisation has registered for GSoC 2021
and how I should start my contribution journey in GNU Compiler Collection.
Thanks and Regards.


Re: GSoC project

2021-02-23 Thread Utkarsh singh via Gcc
Thanks, I'll check it out.

On Mon, Feb 22, 2021 at 12:23 PM Ankur Saini 
wrote:

> I think this is what you are looking for
>
> https://gcc.gnu.org/wiki/SummerOfCode
>
> > On 22-Feb-2021, at 12:08 PM, Utkarsh singh via Gcc 
> wrote:
> >
> > Greeting to the team,
> > I  am Utkarsh Singh. I was going through various projects in the
> > archive section of GSoC. I searched for some specific projects in
> > Mathematics and C programming as I am most used with this field. I feel I
> > can contribute to the organisation which is in turn contributing to the
> > world. I wanted to know if the organisation has registered for GSoC 2021
> > and how I should start my contribution journey in GNU Compiler
> Collection.
> > Thanks and Regards.
>
>


Problems in array access

2021-08-31 Thread Utkarsh Singh via Gcc
Hello GCC mailing list,

In one of my friend's C programming class, they asked him a question on
the topic of array bounds based on the follwing code snippet:

#include 

int main(void)
{
char str[] = {'G' , 'C' , 'C' };
str[3] = '\0' ; /* Isn't this invalid? */
printf("%s\n", str);
}

In an ideal case, str[3] should be a case of out-of-bound array access.
But when compiling the above with -Wall option flag GCC shows no
warning.  So, am I missing something?

Thank you,
Utkarsh Singh

-- 
Utkarsh Singh
http://utkarshsingh.xyz


Re: Problems in array access

2021-08-31 Thread Utkarsh Singh via Gcc
On 2021-08-31, 09:28 +0100, Jonathan Wakely  wrote:

> On Tue, 31 Aug 2021 at 09:11, Utkarsh Singh wrote:
>>
>> Hello GCC mailing list,
>>
>> In one of my friend's C programming class, they asked him a question on
>> the topic of array bounds based on the follwing code snippet:
>>
>> #include 
>>
>> int main(void)
>> {
>> char str[] = {'G' , 'C' , 'C' };
>> str[3] = '\0' ; /* Isn't this invalid? */
>> printf("%s\n", str);
>> }
>>
>> In an ideal case, str[3] should be a case of out-of-bound array access.
>> But when compiling the above with -Wall option flag GCC shows no
>> warning.  So, am I missing something?
>
> This question belongs on the gcc-help mailing list, not here.

Sorry! I will keep this in mind.

> The code has undefined behaviour.
>
> Some GCC warnings depend on checks done during optimization. GCC will
> warn about this code if you use -Wall -O2 and you will get a runtime
> error if you compile with -fsanitize=undefined

Great! And thank you for a quick reply.

-- 
Utkarsh Singh
http://utkarshsingh.xyz


Re: Problems in array access

2021-08-31 Thread Utkarsh Singh via Gcc
On 2021-08-31, 09:08 -0600, Martin Sebor  wrote:

> To refine Jonathan's answer: In cases where the index is constant
> like this one the warning could be issued even with no optimization.
> That it isn't is the result of the choice to depend on optimizations
> unconditionally.  It's worth revisiting this choice in the future.
> If you would like to see such a change for -Warray-bounds (or any
> other warning) please open requests in Bugzilla.

Sure! Currently user account registration is restricted at Bugzilla, I
will request it ASAP.

-- 
Utkarsh Singh
http://utkarshsingh.xyz