On Wed, 7 Dec 2016, Richard Biener wrote:
> >Agreed, that's what I've been using in the past for glibc test cases.
> >
> >If that doesn't work, we'll need something else. Separate compilation
> >of test cases just to thwart compiler optimizations is a significant
> >burden, and will stop working o
On December 7, 2016 6:27:56 PM GMT+01:00, Florian Weimer
wrote:
>* Alexander Monakov:
>
>> On Wed, 7 Dec 2016, Segher Boessenkool wrote:
>>> > For example, this might have impact on writing test for GCC:
>>> >
>>> > When I am writing a test with noinline + noclone then my
>>> > expectation is th
On Wed, Dec 07, 2016 at 06:27:56PM +0100, Florian Weimer wrote:
> >> > When I am writing a test with noinline + noclone then my
> >> > expectation is that no such propagation happens, because
> >> > otherwise a test might turn trivial...
> >>
> >> The usual ways to prevent that are to add some vol
* Alexander Monakov:
> On Wed, 7 Dec 2016, Segher Boessenkool wrote:
>> > For example, this might have impact on writing test for GCC:
>> >
>> > When I am writing a test with noinline + noclone then my
>> > expectation is that no such propagation happens, because
>> > otherwise a test might turn
On 07.12.2016 14:47, Jakub Jelinek wrote:
On Wed, Dec 07, 2016 at 04:12:48PM +0300, Alexander Monakov wrote:
[adding gcc@ for the compiler-testsuite-related discussion, please drop either
gcc@ or gcc-help@ from Cc: as appropriate in replies]
On Wed, 7 Dec 2016, Segher Boessenkool wrote:
For ex
On Wed, Dec 07, 2016 at 04:12:48PM +0300, Alexander Monakov wrote:
> [adding gcc@ for the compiler-testsuite-related discussion, please drop either
> gcc@ or gcc-help@ from Cc: as appropriate in replies]
>
> On Wed, 7 Dec 2016, Segher Boessenkool wrote:
> > > For example, this might have impact on
[adding gcc@ for the compiler-testsuite-related discussion, please drop either
gcc@ or gcc-help@ from Cc: as appropriate in replies]
On Wed, 7 Dec 2016, Segher Boessenkool wrote:
> > For example, this might have impact on writing test for GCC:
> >
> > When I am writing a test with noinline + nocl