From: Jason Merrill <jason@redhat.com>
To: Martin Sebor <msebor@gmail.com>
Cc: "Bernd Edlinger" <bernd.edlinger@hotmail.de>,
"Dominique d'Humières" <dominiq@lps.ens.fr>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Try harder to fix recently introduced crashes in ggc_collect
Date: Mon, 22 May 2017 18:32:00 -0000 [thread overview]
Message-ID: <CADzB+2nw=3KFD2vDGuXZc+02CMwfmPK30p6mvaQoYtHvrvSuyg@mail.gmail.com> (raw)
In-Reply-To: <29c6788f-57b2-927d-a33a-b5be341e37b4@gmail.com>
On Mon, May 22, 2017 at 12:28 PM, Martin Sebor <msebor@gmail.com> wrote:
> On 05/19/2017 11:26 AM, Bernd Edlinger wrote:
>>
>> On 05/19/17 19:05, Dominique d'Humières wrote:
>>>
>>> Hi Bernd,
>>>
>>> Your patches are causing troubles when I try to do "incremental updates
>>> »:
>>>
>>> After revision r248290 it fails with
>>>
>>> ../../work/gcc/cp/init.c:4916:10: fatal error: gt-cp-init.h: No such file
>>> or directory
>>> #include "gt-cp-init.h »
>>>
>>> and after r248242 with
>>>
>>> ../../work/gcc/c-family/c-format.c:4215:10: fatal error:
>>> gt-c-family-c-format.h: No such file or directory
>>> #include "gt-c-family-c-format.h »
>>>
>>> Note that after r248242 a full bootstrap succeeded (don’t know yet for
>>> r248290).
>>>
>>> Is there a way to fix that?
>>>
>>
>> No, unfortunately it looks like incremental does not work in this case.
>>
>> You can try to remove gcc/s-gtyp-input, maybe it un-breaks your
>> build. However, I gave up at that point and did a full bootstrap
>> instead.
>
> I also keep running into this error. Removing my build directory
> and starting from scratch usually fixes it, but it seems that almost
> every time git pull or svn update brings in new changes it comes back.
I've found that the key is ./config.status --recheck so that the
GTFILES variable gets updated from config-lang.in. I'm not sure if
plain ./config.status is also needed, and/or removing the gtype stuff
from the build directory.
Jason
next prev parent reply other threads:[~2017-05-22 18:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 17:25 Dominique d'Humières
2017-05-19 17:31 ` Bernd Edlinger
2017-05-19 18:14 ` Dominique d'Humières
2017-05-22 7:36 ` Richard Biener
2017-05-22 16:55 ` Martin Sebor
2017-05-22 18:32 ` Jason Merrill [this message]
2017-05-22 20:43 ` Jason Merrill
-- strict thread matches above, loose matches on Subject: below --
2017-05-18 15:22 [PATCH] Try " Bernd Edlinger
2017-05-18 15:36 ` Richard Biener
2017-05-18 20:51 ` [PATCH] Try harder " Bernd Edlinger
2017-05-19 0:16 ` Nathan Sidwell
2017-05-19 7:58 ` Richard Biener
2017-05-19 11:06 ` Nathan Sidwell
2017-05-19 14:10 ` Bernd Edlinger
2017-05-19 14:15 ` Nathan Sidwell
2017-05-19 14:34 ` Bernd Edlinger
2017-05-24 11:21 ` Trevor Saunders
2017-05-24 19:12 ` Jason Merrill
2017-05-24 19:29 ` Nathan Sidwell
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='CADzB+2nw=3KFD2vDGuXZc+02CMwfmPK30p6mvaQoYtHvrvSuyg@mail.gmail.com' \
--to=jason@redhat.com \
--cc=bernd.edlinger@hotmail.de \
--cc=dominiq@lps.ens.fr \
--cc=gcc-patches@gcc.gnu.org \
--cc=msebor@gmail.com \
/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).