This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/13896] Initializer string warning not printed if implied NULL-terminator out of bounds
- From: "rhajdaj at yahoo dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 28 Jan 2004 18:13:34 -0000
- Subject: [Bug c/13896] Initializer string warning not printed if implied NULL-terminator out of bounds
- References: <20040128132357.13896.rhajdaj@yahoo.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From rhajdaj at yahoo dot com 2004-01-28 18:13 -------
You're right. This compiler works in agreement with the requirement, so I
should stop bugging you guys. I guess I'm just not seeing the "why" behind the
requirement. When in is it a perfectly acceptable condition (ie according to -
Wall) not to null-terminate a literal string in an array like this? (I don't
understand the "if there's room" part of the requirement.) And who do I talk
to to challenge requirements so I can leave you alone?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13896