Bug 75905 - debug-push-pop-group.c(65) : error C2057: expected constant expression
Summary: debug-push-pop-group.c(65) : error C2057: expected constant expression
Status: RESOLVED FIXED
Alias: None
Product: piglit
Classification: Unclassified
Component: tests (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Windows (All)
: medium blocker
Assignee: Eric Anholt
QA Contact: Eric Anholt
URL:
Whiteboard:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2014-03-08 07:51 UTC by Vinson Lee
Modified: 2014-03-08 09:09 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Vinson Lee 2014-03-08 07:51:09 UTC
piglit: f1dcc2dca67823f2c8d9efed0d63ecebe40bb2a2 (master)

debug-push-pop-group.c
tests\spec\khr_debug\debug-push-pop-group.c(65) : error C2057: expected constant expression
tests\spec\khr_debug\debug-push-pop-group.c(65) : error C2466: cannot allocate an array of constant size 0
tests\spec\khr_debug\debug-push-pop-group.c(65) : error C2133: 'ids' : unknown size
tests\spec\khr_debug\debug-push-pop-group.c(66) : error C2057: expected constant expression
tests\spec\khr_debug\debug-push-pop-group.c(66) : error C2466: cannot allocate an array of constant size 0
tests\spec\khr_debug\debug-push-pop-group.c(66) : error C2133: 'messageLog' : unknown size
tests\spec\khr_debug\debug-push-pop-group.c(77) : warning C4389: '!=' : signed/unsigned mismatch
tests\spec\khr_debug\debug-push-pop-group.c(115) : warning C4204: nonstandard extension used : non-constant aggregate initializer
tests\spec\khr_debug\debug-push-pop-group.c(116) : warning C4204: nonstandard extension used : non-constant aggregate initializer
tests\spec\khr_debug\debug-push-pop-group.c(117) : warning C4204: nonstandard extension used : non-constant aggregate initializer
tests\spec\khr_debug\debug-push-pop-group.c(119) : warning C4204: nonstandard extension used : non-constant aggregate initializer
tests\spec\khr_debug\debug-push-pop-group.c(120) : warning C4204: nonstandard extension used : non-constant aggregate initializer
tests\spec\khr_debug\debug-push-pop-group.c(121) : warning C4204: nonstandard extension used : non-constant aggregate initializer
tests\spec\khr_debug\debug-push-pop-group.c(188) : error C2057: expected constant expression
tests\spec\khr_debug\debug-push-pop-group.c(188) : error C2466: cannot allocate an array of constant size 0
tests\spec\khr_debug\debug-push-pop-group.c(188) : error C2133: 'lengths' : unknown size
tests\spec\khr_debug\debug-push-pop-group.c(189) : error C2057: expected constant expression
tests\spec\khr_debug\debug-push-pop-group.c(189) : error C2466: cannot allocate an array of constant size 0
tests\spec\khr_debug\debug-push-pop-group.c(189) : error C2133: 'messageLog' : unknown size
tests\spec\khr_debug\debug-push-pop-group.c(258) : warning C4018: '<' : signed/unsigned mismatch
tests\spec\khr_debug\debug-push-pop-group.c(275) : warning C4018: '<' : signed/unsigned mismatch


commit f1dcc2dca67823f2c8d9efed0d63ecebe40bb2a2
Author: Timothy Arceri <t_arceri@yahoo.com.au>
Date:   Mon Feb 17 13:29:51 2014 +1100

    KHR_debug: test PushDebugGroup() and PopDebugGroup()
    
    V3:
    - moved piglit_display to end of the file
    - made while() more readable
    - added check for max values of implementation
    - to avoid getting messages we are not interested in
     test_push_pop_debug_group now only filters in the message types we want
    
    v2:
    - add in subtest I accidently removed when tidying the code
    
    Pass: Intel i965 Mesa
    
    Fail: AMD Radeon HD 6670 - Catalyst 13.251
    Catalyst doesnt accept a -1 pararmeter when it should
    
    Signed-off-by: Timothy Arceri <t_arceri@yahoo.com.au>
    Reviewed-by: Fabian Bieler <fabianbieler@fastmail.fm>
Comment 1 Fabian Bieler 2014-03-08 09:03:00 UTC
Should be fixed with 41f537afb37ed86dc51346f9fd412504c6a697f4.
Comment 2 Timothy Arceri 2014-03-08 09:09:24 UTC
Thanks :) I keep forgetting about that.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.