Re: Expensive selftests (was: 'hash_map>')

2021-08-18 Thread David Edelsohn via Gcc-patches
This causes a bootstrap failure for me. PR/101959 On Tue, Aug 17, 2021 at 5:00 AM Richard Biener via Gcc wrote: > > On Tue, Aug 17, 2021 at 8:40 AM Thomas Schwinge > wrote: > > > > Hi! > > > > On 2021-08-16T14:10:00-0600, Martin Sebor wrote: > > > On 8/16/21 6:44 AM, Thomas Schwinge wrote: >

Add more self-tests for 'hash_map' with Value type with non-trivial constructor/destructor (was: Expensive selftests)

2021-08-18 Thread Thomas Schwinge
Hi! On 2021-08-17T10:57:36+0200, Richard Biener wrote: > On Tue, Aug 17, 2021 at 8:40 AM Thomas Schwinge > wrote: >> On 2021-08-16T14:10:00-0600, Martin Sebor wrote: >> > On 8/16/21 6:44 AM, Thomas Schwinge wrote: >> >> [...], to document the current behavior, I propose to >> >> "Add more self

Re: Expensive selftests

2021-08-17 Thread Martin Sebor via Gcc-patches
On 8/17/21 12:40 AM, Thomas Schwinge wrote: Hi! On 2021-08-16T14:10:00-0600, Martin Sebor wrote: On 8/16/21 6:44 AM, Thomas Schwinge wrote: [...], to document the current behavior, I propose to "Add more self-tests for 'hash_map' with Value type with non-trivial constructor/destructor", see a

Re: Expensive selftests (was: 'hash_map>')

2021-08-17 Thread Richard Biener via Gcc-patches
On Tue, Aug 17, 2021 at 8:40 AM Thomas Schwinge wrote: > > Hi! > > On 2021-08-16T14:10:00-0600, Martin Sebor wrote: > > On 8/16/21 6:44 AM, Thomas Schwinge wrote: > >> [...], to document the current behavior, I propose to > >> "Add more self-tests for 'hash_map' with Value type with non-trivial >

Expensive selftests (was: 'hash_map>')

2021-08-16 Thread Thomas Schwinge
Hi! On 2021-08-16T14:10:00-0600, Martin Sebor wrote: > On 8/16/21 6:44 AM, Thomas Schwinge wrote: >> [...], to document the current behavior, I propose to >> "Add more self-tests for 'hash_map' with Value type with non-trivial >> constructor/destructor", see attached. OK to push to master branch

Re: [PATCH] Expensive selftests: torture testing for fix-it boundary conditions (PR c/82050)

2018-01-02 Thread Andreas Schwab
/daten/gcc/gcc-20180101/gcc/testsuite/gcc.dg/plugin/expensive_selftests_plugin.c:175:1: warning: no return statement in function returning non-void [-Wreturn-type] Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now

Re: [PATCH] Expensive selftests: torture testing for fix-it boundary conditions (PR c/82050)

2017-12-11 Thread Jeff Law
ount of coverage, but > the test seems useful, and there seems to be a valid role for "torture" > selftests. > > Hence this patch adds a: > gcc.dg/plugin/expensive_selftests_plugin.c > with the responsibility for running "expensive" selftests, and adds the >

PING: Re: [PATCH] Expensive selftests: torture testing for fix-it boundary conditions (PR c/82050)

2017-12-11 Thread David Malcolm
nacceptable amount of overhead to > add. > > I attempted to optimize the test by reducing the amount of coverage, > but > the test seems useful, and there seems to be a valid role for > "torture" > selftests. > > Hence this patch adds a: > gcc.dg/plug

[PATCH] Expensive selftests: torture testing for fix-it boundary conditions (PR c/82050)

2017-11-28 Thread David Malcolm
Hence this patch adds a: gcc.dg/plugin/expensive_selftests_plugin.c with the responsibility for running "expensive" selftests, and adds the expensive test there. The patch moves a small amount of code from selftest::run_tests into a helper class so that the plugin can print a useful summary line (to