Bug 108515 - tes-gs-max-output.cpp:138: error: expected primary-expression before ‘.’ token
Summary: tes-gs-max-output.cpp:138: error: expected primary-expression before ‘.’ token
Status: RESOLVED FIXED
Alias: None
Product: piglit
Classification: Unclassified
Component: tests (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Piglit Mailing List
QA Contact: Piglit Mailing List
URL:
Whiteboard:
Keywords: bisected, regression
Depends on:
Blocks:
 
Reported: 2018-10-22 17:28 UTC by Vinson Lee
Modified: 2019-03-06 15:33 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Vinson Lee 2018-10-22 17:28:08 UTC
GCC 4.4 build error.

tes-gs-max-output.cpp:138: error: expected primary-expression before ‘.’ token
tes-gs-max-output.cpp:139: error: expected primary-expression before ‘.’ token
tes-gs-max-output.cpp:140: error: expected primary-expression before ‘.’ token
tes-gs-max-output.cpp:141: error: expected primary-expression before ‘.’ token
tes-gs-max-output.cpp:142: error: expected primary-expression before ‘.’ token
tes-gs-max-output.cpp:143: error: expected primary-expression before ‘.’ token
tes-gs-max-output.cpp:144: error: expected primary-expression before ‘.’ token

commit 225b957aa219029e0b6d15e330416557bb1b09ab
Author: Nicolai Hähnle <nicolai.haehnle@amd.com>
Date:   Thu Sep 13 18:24:18 2018 +0200

    arb_tessellation_shader/tes-gs-max-output: new test for TES/GS amplification
    
    Test extremes of GS amplification under tessellation.
    
    Acked-by: Marek Olšák <marek.olsak@amd.com>
Comment 1 Adam Jackson 2019-03-06 15:33:02 UTC
commit 819c122cf7e4b30aeaeba4dc481103247ce30811
Author: Nicolai Hähnle <nicolai.haehnle@amd.com>
Date:   Thu Oct 18 10:28:43 2018 +0200

    Build fix for previous commit
    
    Don't use C++11 features.
    
    Reported-by: Jan Vesely <jan.vesely@rutgers.edu>


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.