Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • L llvm-project
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • CI/CD
    • Code review
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ecpcitest
  • proteas
  • llvm-project
  • Repository
  • llvm-project
  • flang
  • runtime
  • format-implementation.h
Find file Blame History Permalink
  • Peter Klausler's avatar
    [flang] Don't drop format string for external child I/O · e9d0f8ba
    Peter Klausler authored Jan 14, 2022
    In user-defined derived type I/O to an external unit, don't
    omit the format string from the constructor of ChildFormattedIoStatement.
    And include any user IOMSG text in the crash message of the
    parent, if it doesn't catch errors.
    
    Differential Revision: https://reviews.llvm.org/D117903
    e9d0f8ba