# SetupCompiler

## Description

Setup target compiler and its parameters. This dialog allows the user to specify the compiler used to create the program along with the memory model, default calling convention, ABI and other parameters. Please note that while some combinations of the parameters are meaningless, IDA doesn't check them for validity. It is up to the user to specify a correct combination.

IDA tries to determine the correct values automatically.

The include directories are a list of directories that look for the standard C headers. This parameter is used during parsing C header files (the Parse C header file... command; action `LoadHeaderFile`). The directories must be separated by ';' in MS Windows and ':' in Linux. The predefined macros field has the same format and is used similarly. Please note that IDA doesn't define any compiler-specific macros by default.

### Parser options

You can select between different parsers using the parser settings located at the bottom of the **Compiler options** dialog.

![Compiler - Parser options](/files/70D640DmlvJmqegwyWhP)

IDA provides three parser options:

* **legacy** - old internal IDA parser (will be removed in future versions)
* **old\_clang** - previous parser based on clang
* **clang** - new parser introduced in IDA 9.2, (based on LLVM)

### Parser Configuration

The **old\_clang** and new **clang** parser can be fine-tuned using the *Parser specific options* dialog.

![Parser specific options](/files/B0iYvxthcFMuRN1jyqq6)


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.hex-rays.com/ida-actions/setupcompiler.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.