* Required Fields

Recipients email * (separate multiple addresses with commas)

Your name *

Your email *

Message *

Contact Us

* Required Fields
First Name *

Last Name *

Email *

Company / Institution *

Comments: *

 ncsc fails when using C++11 constructs 

Last post Thu, Jul 25 2013 11:42 PM by StephenH. 2 replies.
Started by brandonp 19 Jun 2012 04:37 PM. Topic has 2 replies and 4996 views
Page 1 of 1 (3 items)
Sort Posts:
  • Tue, Jun 19 2012 4:37 PM

    • brandonp
    • Not Ranked
    • Joined on Fri, Oct 2 2009
    • Palo Alto, CA
    • Posts 1
    • Points 20
    ncsc fails when using C++11 constructs Reply

    The GCC version (4.4) that ships with IUS 10.2 (GCC 4.1 is also available) has some C++11 support in it. Using -std=gnu++0x option (-std=c++0x fails due to some ieee header files), the normal C++ compiles work fine, but the NCSC compile fails to even parse those constructs. We are passing -COMPILER g++ and -CFLAGS to ncsc (and -MANUAL), but it's not obvious what frontend is parsing these SystemC/C++ files and whether it contains any C++11 support or not. I did notice that ncsc is running the Edison C++ frontend (edgcpfe), but I don´t know if both it and g++ are being run or not.

    Is it possible at all to use C++11 constructs in SystemC code with IUS 10.2? Some of the constructs available simplify coding quite a bit, and make for more readable/maintainable code.

    [Update: 2012.06.21]

    Running some ncsc commands manually and playing with the options, I found that the options pass to g++/cc1plus properly, but it's the following pass of using edgcpfe that fails. edgcpfe accepts arguments to enable C++0x/C++11 constructs. Is there any way to get those arguments to that process that ncsc spawns?

    Filed under:
    • Post Points: 20
  • Thu, Jul 25 2013 5:46 PM

    • Mark J
    • Not Ranked
    • Joined on Tue, Oct 28 2008
    • Posts 1
    • Points 20
    Re: ncsc fails when using C++11 constructs Reply

    I need to know the answer to this also.  I'm dissapointed that it has been over a year since the original question was posted, and nobody from Cadence has answered it yet.

    • Post Points: 20
  • Thu, Jul 25 2013 11:42 PM

    • StephenH
    • Top 25 Contributor
    • Joined on Tue, Sep 2 2008
    • Bristol, Avon
    • Posts 278
    • Points 4,450
    Re: ncsc fails when using C++11 constructs Reply

     Guys, sorry that nobody answered on the forum. Please bear in mind that for deeply technical or urgent problems you should file a support case at so that an appropriate specialist will take ownership of your case and see it through to completion. By contrast if you post on the public forum and there isn't a suitable C++ expert reading the forum that day, your post may get missed.

    I'm not a C++ expert, but I do use -std=c++0x with Incisive's g++ to access a few of the newer features like maps, and it works for me.

    One thing I would advise is to use a supported version of Incisive; version 10.2 is no longer supported and has been replaced by versions 12.2 and 13.1 (released this month).

    Steve Hobbs / Applications Engineer / Cadence Functional Verification
    • Post Points: 5
Page 1 of 1 (3 items)
Sort Posts:
Started by brandonp at 19 Jun 2012 04:37 PM. Topic has 2 replies.