gcc fixed size char array initialization bug - known?

Hi

I've run across the following gcc "feature":

	char c[4] = "01234";

gcc emits a nice warning

warning: initializer-string for array of chars is too long

But do a

	char c[4] = "0123";

and - a wonder - no warning. No warning with gcc 3.3.2, 3.3.5, 3.4.5, 
4.1.2. I was told 4.2.x does produce a warning. Now do a

	struct {
		char c[4];
		int i;
	} t;
	t.i = 0x12345678;
	strcpy(t.c, c);

and t.i is silently corrupted. Just wanted to ask if this is known, 
really...

Thanks
Guennadi
---
Guennadi Liakhovetski
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: gcc fixed size char array initialization bug - known?
    • From: Jakub Jelinek <[email protected]>
  • Re: gcc fixed size char array initialization bug - known?
    • From: Jan Engelhardt <[email protected]>
  • Re: gcc fixed size char array initialization bug - known?
    • From: Andi Kleen <[email protected]>
  • Re: gcc fixed size char array initialization bug - known?
    • From: Al Viro <[email protected]>
  • Re: gcc fixed size char array initialization bug - known?
    • From: Jan Engelhardt <[email protected]>

• Prev by Date: Re: [PATCH] balance_dirty_pages - exit loop when no more pages available
• Next by Date: Re: unionfs and snmpd kernle bug report
• Previous by thread: unionfs and snmpd kernle bug report
• Next by thread: Re: gcc fixed size char array initialization bug - known?
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]