This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: introduce --param max-vartrack-expr-depth

From: Alexandre Oliva <aoliva at redhat dot com>
To: Bernd Schmidt <bernds at codesourcery dot com>
Cc: gcc-patches at gcc dot gnu dot org
Date: Tue, 31 May 2011 13:13:31 -0300
Subject: Re: introduce --param max-vartrack-expr-depth
References: <or39jw327l.fsf@livre.localdomain> <4DE3784F.6050201@codesourcery.com>

On May 30, 2011, Bernd Schmidt <bernds@codesourcery.com> wrote:

> On 05/30/2011 12:35 PM, Alexandre Oliva wrote:
>> One of my patches for PR 48866 regressed guality/asm-1.c on
>> x86_64-linux-gnu because what used to be a single complex debug value
>> expression became a chain of debug temps holding simpler expressions,
>> and this chain exceeded the default recursion depth in resolving
>> location expressions.

> What's the worst that can happen if you remove the limit altogether?

Exponential behavior comes to mind.  I will try a bootstrap with a very
high value, but for pathological cases we'd probably still need the
param anyway, so I'll check it in.  Thanks for the reviews.

-- 
Alexandre Oliva, freedom fighter    http://FSFLA.org/~lxoliva/
You must be the change you wish to see in the world. -- Gandhi
Be Free! -- http://FSFLA.org/   FSF Latin America board member
Free Software Evangelist      Red Hat Brazil Compiler Engineer

Follow-Ups:
- Re: introduce --param max-vartrack-expr-depth
  - From: Jakub Jelinek

References:
- introduce --param max-vartrack-expr-depth
  - From: Alexandre Oliva
- Re: introduce --param max-vartrack-expr-depth
  - From: Bernd Schmidt

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]