From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29302 invoked by alias); 29 Oct 2012 14:47:46 -0000 Received: (qmail 27898 invoked by uid 48); 29 Oct 2012 14:47:13 -0000 From: "manu at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/55115] [>=4.5.0 regression] missing headers as fatal breaks cproto logic Date: Mon, 29 Oct 2012 14:47:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: preprocessor X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: manu at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Status Resolution Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2012-10/txt/msg02698.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D55115 Manuel L=C3=B3pez-Ib=C3=A1=C3=B1ez changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |RESOLVED Resolution| |INVALID --- Comment #4 from Manuel L=C3=B3pez-Ib=C3=A1=C3=B1ez 2012-10-29 14:47:12 UTC --- (In reply to comment #2) > (In reply to comment #1) > > If the headers do nothing, just delete them? If the headers do somethin= g, how > > can you preprocess the file without the info from the headers? >=20 > That won't work, I believe cproto parses the errors produced by GCC and f= igures > out which declarations are missing based on the errors, then creates a he= ader > containing those declarations. That seems an odd way to generate missing declarations. Missing headers may lead to different code being compiled because of undefined macros, feature = test macros, pragmas, etc. If the header is missing, then ignoring the error will produce exactly the = same result as commenting out the #include. Anyway, not a bug.