This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ 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: [Patch, PR 61061] Add state limit for regex NFA

From: Jonathan Wakely <jwakely at redhat dot com>
To: Maksymilian A <max at cert dot cx>
Cc: timshen at google dot com, libstdc++ at gcc dot gnu dot org, paolo dot carlini at oracle dot com
Date: Thu, 17 Jul 2014 10:38:42 +0100
Subject: Re: [Patch, PR 61061] Add state limit for regex NFA
Authentication-results: sourceware.org; auth=none
References: <CABLZJbw193qGxH7nZYe3fegmH38sEwRBps0E6QDax21zGJPTJQ at mail dot gmail dot com> <20140717093404 dot GQ4871 at redhat dot com>

On 17/07/14 10:34 +0100, Jonathan Wakely wrote:

On 16/07/14 21:46 +0200, Maksymilian A wrote:

Implementation based on vectors are good idea.  It seems to me that this
does not solve all problems. I would like to ask about the
regex_constants::error_type how it's implemented? From the safety point of
view the most important are error_space, error_stack and error_complexity.
In documentation I've found

error_complexity - the complexity of an attempted match against a regular
expression exceeded a pre-set level

How its implemented and where is exactly defined 'pre-set level'? Thanks


error_complexity is not used in our current implementation.


P.S. your original mail was rejected by the list because the GCC lists
only accept plain text email, please do not send html or multipart
emails to the GCC lists.

Follow-Ups:
- Re: [Patch, PR 61061] Add state limit for regex NFA
  - From: Maksymilian A

References:
- Re: [Patch, PR 61061] Add state limit for regex NFA
  - From: Jonathan Wakely

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