On 09/09/2016 04:13 PM, David Malcolm wrote:
On Fri, 2016-09-09 at 14:28 +0200, Florian Weimer wrote:
For compile-time fortify checks (such as the wrappers for type-safe
open/openat), we need to add tests in glibc which examine the
compiler
output for warnings and errors.
I do not want to add
On 09.09.2016 21:15, Manuel López-Ibáñez wrote:
> On 09/09/16 13:28, Florian Weimer wrote:
>> For compile-time fortify checks (such as the wrappers for type-safe
>> open/openat), we need to add tests in glibc which examine the compiler output
>> for warnings and errors.
>>
>> I do not want to add
On 09/09/2016 06:28 AM, Florian Weimer wrote:
For compile-time fortify checks (such as the wrappers for type-safe
open/openat), we need to add tests in glibc which examine the compiler
output for warnings and errors.
I do not want to add Dejagnu as a dependency to the glibc test suite,
but I
On Fri, 9 Sep 2016, David Malcolm wrote:
> (FWIW, I'd much prefer it if DejaGnu were implemented in Python rather
> than Tcl; writing and debugging .exp files below gcc/testsuite is one
QMTest was a test harness written in Python and avoiding various issues
with DejaGnu's design, though by now
On Fri, 2016-09-09 at 14:28 +0200, Florian Weimer wrote:
> For compile-time fortify checks (such as the wrappers for type-safe
> open/openat), we need to add tests in glibc which examine the
> compiler
> output for warnings and errors.
>
> I do not want to add Dejagnu as a dependency to the
For compile-time fortify checks (such as the wrappers for type-safe
open/openat), we need to add tests in glibc which examine the compiler
output for warnings and errors.
I do not want to add Dejagnu as a dependency to the glibc test suite,
but I wonder if you could share any lessons learned
