Re: [libvirt] [PATCH] Raise the frame limit for tests

2018-01-22 Thread Michal Privoznik
On 01/22/2018 02:34 PM, Daniel P. Berrange wrote: > On Mon, Jan 22, 2018 at 02:28:42PM +0100, Martin Kletzander wrote: >> On Mon, Jan 22, 2018 at 12:57:31PM +, Daniel P. Berrange wrote: >>> On Mon, Jan 22, 2018 at 01:54:28PM +0100, Martin Kletzander wrote: On Mon, Jan 22, 2018 at

Re: [libvirt] [PATCH] Raise the frame limit for tests

2018-01-22 Thread Daniel P. Berrange
On Mon, Jan 22, 2018 at 02:28:42PM +0100, Martin Kletzander wrote: > On Mon, Jan 22, 2018 at 12:57:31PM +, Daniel P. Berrange wrote: > > On Mon, Jan 22, 2018 at 01:54:28PM +0100, Martin Kletzander wrote: > > > On Mon, Jan 22, 2018 at 01:47:24PM +0100, Michal Privoznik wrote: > > > > On

Re: [libvirt] [PATCH] Raise the frame limit for tests

2018-01-22 Thread Martin Kletzander
On Mon, Jan 22, 2018 at 02:01:27PM +0100, Michal Privoznik wrote: On 01/22/2018 01:54 PM, Martin Kletzander wrote: On Mon, Jan 22, 2018 at 01:47:24PM +0100, Michal Privoznik wrote: On 01/22/2018 01:22 PM, Daniel P. Berrange wrote: On Mon, Jan 22, 2018 at 12:49:12PM +0100, Martin Kletzander

Re: [libvirt] [PATCH] Raise the frame limit for tests

2018-01-22 Thread Martin Kletzander
On Mon, Jan 22, 2018 at 12:57:31PM +, Daniel P. Berrange wrote: On Mon, Jan 22, 2018 at 01:54:28PM +0100, Martin Kletzander wrote: On Mon, Jan 22, 2018 at 01:47:24PM +0100, Michal Privoznik wrote: > On 01/22/2018 01:22 PM, Daniel P. Berrange wrote: > > On Mon, Jan 22, 2018 at 12:49:12PM

Re: [libvirt] [PATCH] Raise the frame limit for tests

2018-01-22 Thread Michal Privoznik
On 01/22/2018 01:54 PM, Martin Kletzander wrote: > On Mon, Jan 22, 2018 at 01:47:24PM +0100, Michal Privoznik wrote: >> On 01/22/2018 01:22 PM, Daniel P. Berrange wrote: >>> On Mon, Jan 22, 2018 at 12:49:12PM +0100, Martin Kletzander wrote: On Thu, Jan 18, 2018 at 10:16:55AM +0100, Ján Tomko

Re: [libvirt] [PATCH] Raise the frame limit for tests

2018-01-22 Thread Daniel P. Berrange
On Mon, Jan 22, 2018 at 01:54:28PM +0100, Martin Kletzander wrote: > On Mon, Jan 22, 2018 at 01:47:24PM +0100, Michal Privoznik wrote: > > On 01/22/2018 01:22 PM, Daniel P. Berrange wrote: > > > On Mon, Jan 22, 2018 at 12:49:12PM +0100, Martin Kletzander wrote: > > > > On Thu, Jan 18, 2018 at

Re: [libvirt] [PATCH] Raise the frame limit for tests

2018-01-22 Thread Martin Kletzander
On Mon, Jan 22, 2018 at 01:47:24PM +0100, Michal Privoznik wrote: On 01/22/2018 01:22 PM, Daniel P. Berrange wrote: On Mon, Jan 22, 2018 at 12:49:12PM +0100, Martin Kletzander wrote: On Thu, Jan 18, 2018 at 10:16:55AM +0100, Ján Tomko wrote: After the latest CPU additions, the build fails

Re: [libvirt] [PATCH] Raise the frame limit for tests

2018-01-22 Thread Michal Privoznik
On 01/22/2018 01:22 PM, Daniel P. Berrange wrote: > On Mon, Jan 22, 2018 at 12:49:12PM +0100, Martin Kletzander wrote: >> On Thu, Jan 18, 2018 at 10:16:55AM +0100, Ján Tomko wrote: >>> After the latest CPU additions, the build fails with clang: >>> cputest.c:905:1: error: stack frame size of 26136

Re: [libvirt] [PATCH] Raise the frame limit for tests

2018-01-22 Thread Daniel P. Berrange
On Mon, Jan 22, 2018 at 12:49:12PM +0100, Martin Kletzander wrote: > On Thu, Jan 18, 2018 at 10:16:55AM +0100, Ján Tomko wrote: > > After the latest CPU additions, the build fails with clang: > > cputest.c:905:1: error: stack frame size of 26136 bytes > > in function 'mymain'

Re: [libvirt] [PATCH] Raise the frame limit for tests

2018-01-22 Thread Martin Kletzander
On Thu, Jan 18, 2018 at 10:16:55AM +0100, Ján Tomko wrote: After the latest CPU additions, the build fails with clang: cputest.c:905:1: error: stack frame size of 26136 bytes in function 'mymain' [-Werror,-Wframe-larger-than=] Raise the relaxed limit which is used for tests. ---

[libvirt] [PATCH] Raise the frame limit for tests

2018-01-18 Thread Ján Tomko
After the latest CPU additions, the build fails with clang: cputest.c:905:1: error: stack frame size of 26136 bytes in function 'mymain' [-Werror,-Wframe-larger-than=] Raise the relaxed limit which is used for tests. --- m4/virt-compile-warnings.m4 | 2 +- 1 file changed, 1 insertion(+), 1