From: Nathan Sidwell <nathan@acm.org>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: Richard Biener <richard.guenther@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Kill -fdump-translation-unit
Date: Thu, 11 May 2017 17:48:00 -0000 [thread overview]
Message-ID: <a40dca72-b173-d65c-788d-a99ee536988b@acm.org> (raw)
In-Reply-To: <yddo9uzi9il.fsf@CeBiTec.Uni-Bielefeld.DE>
[-- Attachment #1: Type: text/plain, Size: 343 bytes --]
On 05/11/2017 01:33 PM, Rainer Orth wrote:
> unfortunately, this part
>
> * graphite-poly.c: Don't include tree-dump.h.
>
> broke bootstrap with graphite:
oh, that has to be configured enabled? I've committed this that I think
is obvious. looks to be another case of using tree-dumph to get at
dumpfile.h.
nathan
--
Nathan Sidwell
[-- Attachment #2: inc.diff --]
[-- Type: text/x-patch, Size: 462 bytes --]
2017-05-11 Nathan Sidwell <nathan@acm.org>
* graphite-poly.c: Include dumpfile.h.
Index: graphite-poly.c
===================================================================
--- graphite-poly.c (revision 247916)
+++ graphite-poly.c (working copy)
@@ -40,6 +40,7 @@ along with GCC; see the file COPYING3.
#include "pretty-print.h"
#include "gimple-pretty-print.h"
#include "graphite.h"
+#include "dumpfile.h"
/* Print to STDERR the GMP value VAL. */
next prev parent reply other threads:[~2017-05-11 17:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 15:46 Nathan Sidwell
2017-05-10 8:58 ` Richard Biener
2017-05-10 17:51 ` Alexander Monakov
2017-05-10 17:59 ` Jakub Jelinek
2017-05-10 20:57 ` Alexander Monakov
2017-05-10 21:59 ` Nathan Sidwell
2017-05-11 15:52 ` Nathan Sidwell
2017-05-11 17:37 ` Rainer Orth
2017-05-11 17:48 ` Nathan Sidwell [this message]
2017-05-11 17:50 ` Rainer Orth
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=a40dca72-b173-d65c-788d-a99ee536988b@acm.org \
--to=nathan@acm.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
/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).