search for: frontendoptions

...angFrontendTool. Driver.h and Compilation.h from libClangDriver are responsible to call, pass the correct arguments and execute the driver. TextDiagnosticPrinter.h takes care of printing the driver diagnostics in case of errors. The Flang frontend will use CompilerInstance, CompilerInvocation, FrontendOptions, FrontendActions and Utils from libClangFrontend and libClangFrontendTool. These methods are responsible for translating the command line arguments to frontend Options and later to Actions to be executed by ExecuteCompilerInvocation. The translation from arguments to Actions happens with Fronte...

...gt; from libClangDriver are responsible to call, pass the correct arguments >> and execute the driver. TextDiagnosticPrinter.h takes care of printing >> the driver diagnostics in case of errors. >> >> The Flang frontend will use CompilerInstance, CompilerInvocation, >> FrontendOptions, FrontendActions and Utils from libClangFrontend and >> libClangFrontendTool. These methods are responsible for translating the >> command line arguments to frontend Options and later to Actions to be >> executed by ExecuteCompilerInvocation. The translation from arguments to >...

Hey all, I'm compiling a bunch of files through a clang CompilerInvocation and I want the results in a buffer (rather than on a file). In order to get the output out of a compile invocation, one normally sets FrontendOptions.OutputFile but on my environment, I don't want a file to be created. I want to do post-processing myself before creating output. Anyone has any ideas?

...ct arguments > and execute the driver. TextDiagnosticPrinter.h takes care > of printing > the driver diagnostics in case of errors. > > The Flang frontend will use CompilerInstance, > CompilerInvocation, > FrontendOptions, FrontendActions and Utils from > libClangFrontend and > libClangFrontendTool. These methods are responsible for > translating the > command line arguments to frontend Options and later to > Actions to be > ex...