Compiler optimizes away certain calls to assert()

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: High
    • Code Generation Tools
    • CODEGEN-332
    • SDSCM00041434
    • Hide
      C6000_7.4.0B1
      ARP32_1.0.0B1
      Show
      C6000_7.4.0B1 ARP32_1.0.0B1
    • Hide
      C6000_7.4.0
      ARP32_1.0.0B3
      Show
      C6000_7.4.0 ARP32_1.0.0B3
    • Hide
      Instead of "assert(p)", use "if (!p) assert(0)", which will still abort
      at the same place under the same conditions, but will have a different
      error message. More elaborately, implement a function equivalent to
      assert() but with a different name, that the compiler will not recognise
      as a system function.
      Show
      Instead of "assert(p)", use "if (!p) assert(0)", which will still abort at the same place under the same conditions, but will have a different error message. More elaborately, implement a function equivalent to assert() but with a different name, that the compiler will not recognise as a system function.

      Compiler optimizes away certain calls to assert()

            Assignee:
            TI User
            Reporter:
            TI User
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:

                Connection: Intermediate to External PROD System
                EXTSYNC-367 - Compiler optimizes away certain cal...
                SYNCHRONIZED
                • Last Sync Date: