Item request has been placed! ×
Item request cannot be made. ×
loading  Processing Request

A synchronous language with partial delay specification for real-time systems programming

Item request has been placed! ×
Item request cannot be made. ×
loading   Processing Request
Read More Add to Saved list
  • Additional Information
    • Contributors:
      ONERA - The French Aerospace Lab Toulouse; ONERA; Ecole Nationale Supérieure d'Electrotechnique, d'Electronique, d'Informatique, d'Hydraulique et de Télécommunications (ENSEEIHT); Institut National Polytechnique (Toulouse) (Toulouse INP); Université de Toulouse (UT)-Université de Toulouse (UT); Contributions of the Data parallelism to real time (DART); Laboratoire d'Informatique Fondamentale de Lille (LIFL); Université de Lille, Sciences et Technologies-Institut National de Recherche en Informatique et en Automatique (Inria)-Université de Lille, Sciences Humaines et Sociales-Centre National de la Recherche Scientifique (CNRS)-Université de Lille, Sciences et Technologies-Institut National de Recherche en Informatique et en Automatique (Inria)-Université de Lille, Sciences Humaines et Sociales-Centre National de la Recherche Scientifique (CNRS)-Inria Lille - Nord Europe; Institut National de Recherche en Informatique et en Automatique (Inria)
    • Publication Information:
      HAL CCSD
    • Publication Date:
      2012
    • Collection:
      ONERA: HAL (Centre français de recherche aérospatiale / French Aerospace Lab)
    • Subject Terms:
      Kyoto; Japan
    • Subject Terms:
      Kyoto, Japan
    • Abstract:
      International audience ; High-level formal programming languages require system designers to provide a very precise description of the system during early development phases, which may in some cases lead to arbitrary choices (i.e. the designer "overspecifies" the system). In this paper, we propose an extension of synchronous dataflow languages where the designer can specify that he does not care whether some communication is immediate or delayed. It is then up to the compiler to choose where to introduce delays, in a way that breaks causality cycles and satisfies latency requirements imposed on the system.
    • Relation:
      hal-00800975; https://hal.science/hal-00800975; https://hal.science/hal-00800975/document; https://hal.science/hal-00800975/file/wyss12-APLAS.pdf
    • Online Access:
      https://hal.science/hal-00800975
      https://hal.science/hal-00800975/document
      https://hal.science/hal-00800975/file/wyss12-APLAS.pdf
    • Rights:
      info:eu-repo/semantics/OpenAccess
    • Accession Number:
      edsbas.12B34CD7