This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/33933] "error: array type has incomplete element type" in system header
- From: "joseph at codesourcery dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 28 Oct 2007 21:13:57 -0000
- Subject: [Bug c/33933] "error: array type has incomplete element type" in system header
- References: <bug-33933-276@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #2 from joseph at codesourcery dot com 2007-10-28 21:13 -------
Subject: Re: New: "error: array type has incomplete element
type" in system header
On Sun, 28 Oct 2007, danglin at gcc dot gnu dot org wrote:
> This was discussed in this thread:
> http://gcc.gnu.org/ml/gcc/2005-02/msg00054.html
>
> In particular, the following DR was referenced as proof the above is
> "not valid C":
> http://www.open-std.org/jtc1/sc22/wg14/www/docs/dr_047.html
>
> It says there regarding the submitted examples that "First of
> all, no constraints are violated. Therefore, no diagnostics are required."
A constraint was added in C99.
> So, I'm questioning why a -pedantic warning was changed to a hard error
> in gcc 4.0.0. This seems to have been ignored in Joseph's response
> and the subsequent change.
I referenced bug 19333 in my message you reference above; it's an ICE
showing the former undocumented extension did not work (the original bug
summary was "Compilation SEGFAULTs with -O1 -finline-functions on the
x86_64 architecture."). That in turn links to gcc-patches discussions
leading to it becoming a hard error.
The system header issue could be fixed by fixincludes.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33933