On Thu, Feb 23, 2017 at 07:57:41AM -0500, Ronald S. Bultje wrote:
> Hi,
>
> On Thu, Feb 23, 2017 at 2:19 AM, wm4 wrote:
>
> > On Wed, 22 Feb 2017 19:16:46 +0100
> > Michael Niedermayer wrote:
> >
> > > This enables the extra error messages in case of DEBUG or high assrtion
> > levels.
> > > Hig
On Thu, 23 Feb 2017 07:57:41 -0500
"Ronald S. Bultje" wrote:
> Hi,
>
> On Thu, Feb 23, 2017 at 2:19 AM, wm4 wrote:
>
> > On Wed, 22 Feb 2017 19:16:46 +0100
> > Michael Niedermayer wrote:
> >
> > > This enables the extra error messages in case of DEBUG or high assrtion
> > levels.
> > >
Hi,
On Thu, Feb 23, 2017 at 2:19 AM, wm4 wrote:
> On Wed, 22 Feb 2017 19:16:46 +0100
> Michael Niedermayer wrote:
>
> > This enables the extra error messages in case of DEBUG or high assrtion
> levels.
> > High assertion levels imply slow checks in inner loops so any extra
> error should
> > be
On Wed, 22 Feb 2017 19:16:46 +0100
Michael Niedermayer wrote:
> This enables the extra error messages in case of DEBUG or high assrtion
> levels.
> High assertion levels imply slow checks in inner loops so any extra error
> should
> be insignificant.
> Is it preferred to have a separate switch
On 2/22/17, Michael Niedermayer wrote:
> This enables the extra error messages in case of DEBUG or high assrtion
> levels.
> High assertion levels imply slow checks in inner loops so any extra error
> should
> be insignificant.
> Is it preferred to have a separate switch for ff_elog() so it doesnt
This enables the extra error messages in case of DEBUG or high assrtion levels.
High assertion levels imply slow checks in inner loops so any extra error should
be insignificant.
Is it preferred to have a separate switch for ff_elog() so it doesnt depend on
DEBUG/assertion level ?
Signed-off-by: M
