On Wed, Nov 20, 2024 at 09:43:46PM +0530, AKASH MISHRA via Gcc-bugs wrote:
> Hi Team,
> there is a bug , compiler not reporting error or warning while calling a
> function with parentheses.
>
> For ex:
>
> void func()
> {
> printf("Hi i am in func");
> }
>
> main()
> {
> // call the func here wi
On Wed, Jul 06, 2022 at 10:15:51AM +1000, Norman wrote:
> Hi all,
>
> Consider this bit of code:
>
> unsigned int d=1,e=2,f;
>
> if((d-e) < 0)
> {
> f=d-e;
> printf("f=%i",f);
> }
>
> gcc -Wall -DLinux -D_FILE_OFFSET_BITS=64 -c scroll.c
>
> gcc compiles thi
On Tue, Sep 15, 2020 at 10:41:31PM +0100, Nuno Gonçalves via Gcc-bugs wrote:
> Hi Jason et al,
>
> After a bisect I found that the commit
> 7fc49a5777943aab11e227136d00a836f28f12b2 causes a segmentation fault
> during my compilation:
This is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96805
> s
On Sat, Apr 21, 2018 at 11:47:52AM +0200, Dávid Bolvanský wrote:
> Hello,
>
> #include
> int main(void)
> {
> char buf[10];
> return snprintf(buf, 0, "string");
> }
>
> GCC simplifies it to
> main:
> mov eax, 6
> ret
>
> but 0 is correct I think.
No, 6 seems to be the correct value:
If the out
On Tue, May 06, 2014 at 06:33:03PM +, peter_e at gmx dot net wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=61081
>
> --- Comment #2 from Peter Eisentraut ---
> No, these "functions" need to have a usable return value, because someone
> could
> write
>
> if (!sigemptyset(...))
> w
