> For the complete documentation index, see [llms.txt](https://docs.hex-rays.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hex-rays.com/9.1/user-guide/signatures/flirt/supported-compilers.md).

# Supported Compilers

## Supported C Compilers

* Aztec C v3.20d
* Borland C++ for OS/2 v1.0, v1.5, v2.0
* Borland Turbo C v2.0, v2.01
* Borland Turbo C++ v1.01
* Borland C++ v2.0, v3.1, v4.0, v4.5, v5.0, v5.01
* Borland C++ Builder v1.0
* Borland C++ Builder v3.0
* EMX (GCC) for OS/2 v0.9b
* IBM C Set v2.00, v2.10
* IBM Visual Age C++ v3.0 OS/2
* Lattice C v3.30
* Metaware High C for OS/2
* Microsoft C v5.0, v6.0, v7.0 Microsoft Quick C v1.0, v2.01
* Microsoft Visual C++ v1.0, v1.5, v2.0, v4.0, v4.1, v5 and v6
* NDP C v4.2
* Optima v1.0
* Symantec C++ v6.0, 6.1, 7.2
* Texas Instruments C Compiler for TMS320C6
* Visual Age C++ v3.0
* Visual Age C++ v3.5
* Watcom C++ v9.01d, v9.5, v10.0,
* v10.0b, v10.5, v10.6
* Watcom for QNX
* Zortech C v1.0, v3.1
* Microsoft Visual C++ v7, 8 (Microsoft.NET)
* Microsoft 64-bit Visual C++ AMD64
* Microsoft Visual C++ for Windows CE v3-4.2 on ARM
* Borland C++ Build v1-6
* GNU C compilers on various platforms

## Supported Pascal Compilers

* Borland Turbo Pascal 5, 5.5, 6, 7, Borland Turbo Pascal for Windows
* Borland Delphi 1, Delphi 2, Delphi 3, Delphi 4, Delphi 5

## Supported Fortran Compilers

* MS Fortran PowerStation 4.0

## Supported Libraries

* Microsoft Foundation Classes
* Borland 5.0x MFC adaptation, Borland Visual Component Library
* CTask
* SDK CAB Library
* Vireo Libraries Borland Edition and MicroSoft Edition
* Object Toolkit Pro
* Windows CE libraries
* Keil runtime libraries for C166
* C runtime library for I960
* C runtime for TMS320C6
* Borland 6.0x Visual Component Library

## How does it work ?

Have a look at the Flirt [technical paper](/9.1/user-guide/signatures/flirt/ida-f.l.i.r.t.-technology-in-depth.md)!


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hex-rays.com/9.1/user-guide/signatures/flirt/supported-compilers.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.