This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug rtl-optimization/72855] Long compile time due to integrity checking during dataflow analysis per loop
- From: "rguenther at suse dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 10 Aug 2016 18:36:29 +0000
- Subject: [Bug rtl-optimization/72855] Long compile time due to integrity checking during dataflow analysis per loop
- Auto-submitted: auto-generated
- References: <bug-72855-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72855
--- Comment #9 from rguenther at suse dot de <rguenther at suse dot de> ---
On August 10, 2016 7:20:00 PM GMT+02:00, "dje at gcc dot gnu.org"
<gcc-bugzilla@gcc.gnu.org> wrote:
>https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72855
>
>David Edelsohn <dje at gcc dot gnu.org> changed:
>
> What |Removed |Added
>----------------------------------------------------------------------------
> Status|UNCONFIRMED |NEW
> Last reconfirmed| |2016-08-10
> Ever confirmed|0 |1
>
>--- Comment #8 from David Edelsohn <dje at gcc dot gnu.org> ---
>> Yes, but that is guarded by flag_checking which defaults to 0.
>
>How can flag_checking be 0 if -fno-checking has an effect?
It can't have an effect with release checking unless sth is seriously botched.
Which is why I asked this to be investigated (I can't reproduce it on x86_64
Linux)