1. 20 Apr, 2018 2 commits
  2. 06 Jun, 2017 1 commit
  3. 21 May, 2017 1 commit
    • Simon Schuster's avatar
      Bugfix: Platina-Intrinsic: pass type/expr by operand · 3f8fbb08
      Simon Schuster authored
      The former implementation passed the platina type and expression
      infromation by means of two metadata items attached to the intrinsic
      call instruction. However, the tail-call-optimization dropped this
      metadata (in sync with the docs):
      
        A transformation is required to drop any metadata attachment that it
        does not know or know it can’t preserve.
      
      Passing this data by means of operands to the call instruction should
      be more robust.
      3f8fbb08
  4. 15 May, 2017 1 commit
  5. 13 May, 2017 2 commits
  6. 12 May, 2017 2 commits
  7. 06 May, 2017 2 commits
    • Simon Schuster's avatar
      Export the extracted PlatinaFacts to PML · 3ccd7132
      Simon Schuster authored
      The facts are exported to the modelfacts member in the PML-files.
      Syntax is as follows:
      
      ```YAML
      modelfacts:
        - program-point:
            function:        c_entry
            block:           if.else
          origin:          platina.bc
          level:           bitcode
          type:            guard
          expression:      'false'
      ```
      3ccd7132
    • Simon Schuster's avatar
      Add a new Platina intrinsic · 5b105ce7
      Simon Schuster authored
      This commit adds a platina intrinsic, which is used as metadata
      container for annotations. This container degrades to a simple platina
      intrinsic opcode, with no parameters.
      This switch from Bitcode to Machinecode happens in
      CodeGen/SelectionDAG, which the metadata.
      We prohibit this opcode from lowering.
      5b105ce7
  8. 22 Apr, 2017 2 commits
    • Simon Schuster's avatar
      Bugfix: YAML-export, remove default Linkage · 1ee5f421
      Simon Schuster authored
      Linkage information on Functions with `ExternalLinkage` was not emitted
      to YAML.
      
      From the docs:
      	http://llvm.org/docs/YamlIO.html
      "There is one important difference between those two ways (default
      constructor and third parameter to mapOptional). When YAML I/O generates
      a YAML document, if the mapOptional() third parameter is used, if the
      actual value being written is the same as (using ==) the default value,
      then that key/value is not written."
      1ee5f421
    • Simon Schuster's avatar
      Export function linkage information to PMLs · 5bfb7c40
      Simon Schuster authored
      This commit exports a functions LinkageType to PML for both
      MachineFunctions and BitcodeFunctions.
      5bfb7c40
  9. 19 Apr, 2017 1 commit
  10. 18 Apr, 2017 1 commit
  11. 11 Apr, 2017 1 commit
  12. 10 Apr, 2017 11 commits
  13. 09 Apr, 2017 6 commits
  14. 09 Jul, 2016 4 commits
  15. 15 Apr, 2016 1 commit
  16. 16 Mar, 2016 2 commits