From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-451572-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 20365 invoked by alias); 14 May 2014 08:51:43 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Received: (qmail 20274 invoked by uid 48); 14 May 2014 08:51:40 -0000
From: "doko at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug plugins/61176] [4.9/4.10 Regression] plugin builds including gimple.h not building
Date: Wed, 14 May 2014 08:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: plugins
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: doko at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.9.1
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-61176-4-GutL1aihMR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61176-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61176-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-05/txt/msg01264.txt.bz2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61176

--- Comment #2 from Matthias Klose <doko at gcc dot gnu.org> ---
is this about stability? With trying, you find out that the following will
work:

#include <gcc-plugin.h>
#include <tree.h>
#include <function.h>
#include <basic-block.h>
#include <coretypes.h>
#include <is-a.h>
#include <predict.h>
#include <internal-fn.h>
#include <tree-ssa-alias.h>
#include <gimple-expr.h>
#include <gimple.h>

int main(void) {
        return 0;
}


is there any way to find out all the needed includes?  Telling plugin writers
to hard-code all of this doesn't seem like a viable solution.