From: "Dominique d'Humières" <dominiq@lps.ens.fr>
To: Eric Botcazou <ebotcazou@adacore.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: Restore functional DONT_USE_BUILTIN_SETJMP support
Date: Tue, 10 Oct 2017 10:57:00 -0000 [thread overview]
Message-ID: <C7474A3B-C039-45C1-96C3-424EC3D01D6E@lps.ens.fr> (raw)
In-Reply-To: <10399575.CIq72W5JSa@polaris>
> Le 10 oct. 2017 à 11:53, Eric Botcazou <ebotcazou@adacore.com> a écrit :
>
>> This cause
>>
>> % /opt/gcc/gcc8w/bin/g++ -std=c++11 -O2 -fnon-call-exceptions
>> /opt/gcc/work/gcc/testsuite/g++.dg/pr62079.C -c -m32
>> /opt/gcc/work/gcc/testsuite/g++.dg/pr62079.C: In function 'int main()':
>> /opt/gcc/work/gcc/testsuite/g++.dg/pr62079.C:78:1: error: non-cold basic
>> block 5 reachable only by paths crossing the cold partition }
>> ^
>> during RTL pass: split2
>> /opt/gcc/work/gcc/testsuite/g++.dg/pr62079.C:78:1: internal compiler error:
>> verify_flow_info failed
>>
>> on x86_64-apple-darwin16.
>
> Really sure? The patch is a no-op except for IA-64 and Aarch64.
After verification, you are right: the problem is older but requires the compiler to be configured with
--enable-checking=yes.
Sorry for the noise.
Dominique
>
> --
> Eric Botcazou
next prev parent reply other threads:[~2017-10-10 10:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 8:44 Dominique d'Humières
2017-10-10 10:34 ` Eric Botcazou
2017-10-10 10:57 ` Dominique d'Humières [this message]
2017-10-10 11:59 ` Eric Botcazou
-- strict thread matches above, loose matches on Subject: below --
2017-10-08 10:57 Eric Botcazou
2017-10-08 14:18 ` Andreas Schwab
2017-10-09 2:13 ` Joseph Myers
2017-10-08 16:38 ` Andreas Schwab
2017-10-08 20:52 ` Eric Botcazou
2017-10-09 22:56 ` Eric Botcazou
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=C7474A3B-C039-45C1-96C3-424EC3D01D6E@lps.ens.fr \
--to=dominiq@lps.ens.fr \
--cc=ebotcazou@adacore.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).