From: Aldy Hernandez <aldyh@redhat.com>
To: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: [java] include missing file after debug-early merge
Date: Fri, 05 Jun 2015 19:37:00 -0000 [thread overview]
Message-ID: <5571F847.8060900@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 262 bytes --]
Must've crossed paths with Andrew Macleod in his header refactoring or
something. I added a call to global_decl_processing() which is now
missing the relevant header file.
I'm testing this and committing as obvious, once I retest mainline once
again.
Aldy
[-- Attachment #2: curr --]
[-- Type: text/plain, Size: 530 bytes --]
commit d681ceeaef7dcc598a469d86c60e370c21a4f4ed
Author: Aldy Hernandez <aldyh@redhat.com>
Date: Fri Jun 5 15:24:49 2015 -0400
* jcf-parse.c: Include toplev.h.
diff --git a/gcc/java/jcf-parse.c b/gcc/java/jcf-parse.c
index ba216a1..721696b 100644
--- a/gcc/java/jcf-parse.c
+++ b/gcc/java/jcf-parse.c
@@ -55,6 +55,7 @@ The Free Software Foundation is independent of Sun Microsystems, Inc. */
#include "cgraph.h"
#include "bitmap.h"
#include "target.h"
+#include "toplev.h"
#ifdef HAVE_LOCALE_H
#include <locale.h>
reply other threads:[~2015-06-05 19:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5571F847.8060900@redhat.com \
--to=aldyh@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).