search for: cc1option

...ver/Options.td b/include/clang/Driver/Options.td index a2be903..da932e2 100644 --- a/include/clang/Driver/Options.td +++ b/include/clang/Driver/Options.td @@ -351,6 +351,10 @@ def fno_autolink : Flag <["-"], "fno-autolink">, Group<f_Group>, Flags<[DriverOption, CC1Option]>, HelpText<"Disable generation of linker directives for automatic library linking">; +def fauto_profile : Flag<["-"], "fauto-profile">, Group<f_Group>, + Flags<[DriverOption, CC1Option]>, + HelpText<"Enable automatic profil...

Hello all! I have found following empty files that get installed (v3.4rc2) : docs/llvm/html/Dummy.html include/clang/Driver/CC1Options.h What is the story behind them? Or were they just forgotten? Can we (someone) remove these? Cheers, Gabor

.../Driver/Options.td > index a2be903..da932e2 100644 > --- a/include/clang/Driver/Options.td > +++ b/include/clang/Driver/Options.td > @@ -351,6 +351,10 @@ def fno_autolink : Flag <["-"], "fno-autolink">, > Group<f_Group>, > Flags<[DriverOption, CC1Option]>, > HelpText<"Disable generation of linker directives for automatic > library linking">; > > +def fauto_profile : Flag<["-"], "fauto-profile">, Group<f_Group>, > + Flags<[DriverOption, CC1Option]>, > + HelpText<...

Hi, I have been writing a hobbie code generator for a plc with clang as a front end and I wanted to know how can I get clang to accept a new code generator option, and how to get it through to the code generator. I found something that could be it on an llvm include "TargetOptions" but I have no idea how to use it (if it is actually correct). Thanks

...1, 0) ///< Run loop vectorizer. CODEGENOPT(VectorizeSLP , 1, 0) ///< Run SLP vectorizer. +CODEGENOPT(IsPreIPO , 1, 0) ///< Indicate in pre-IPO phase /// Attempt to use register sized accesses to bit-fields in structures, when /// possible. Index: include/clang/Driver/CC1Options.td =================================================================== --- include/clang/Driver/CC1Options.td (revision 187135) +++ include/clang/Driver/CC1Options.td (working copy) @@ -210,6 +210,8 @@ HelpText<"Run the SLP vectorization passes">; def vectorize_slp_aggressive :...

Andy and I briefly discussed this the other day, we have not yet got chance to list a detailed pass order for the pre- and post- IPO scalar optimizations. This is wish-list in our mind: pre-IPO: based on the ordering he propose, get rid of the inlining (or just inline tiny func), get rid of all loop xforms... post-IPO: get rid of inlining, or maybe we still need it, only

Hello, I have tried a lot fix this error but am not able to can you please find me a solution am trying to compile the SAFECode in Cygwin Environment to work for windows. used make -j4 command to make the files in cygwin i have got this error make[5]: Leaving directory '/home/uidr7475/Work/LLVM_OBJ/projects/safecode/tools/clang/include' /usr/bin/cp: cannot stat

...via the diagnostics layer, > source locations). > > This will require some decoupling between the Clang driver and frontend > (currently Clang's Options.td contains various driver options that are > marked as also being options for Clang's -cc1 mode; duplicating those in > CC1Options.td is probably acceptable, if we're going to split the driver > and frontend into two different projects), and some shared support code > (eg, clang's sanitizers list) will presumably end up in the driver, because > we don't want a driver -> *lang dependency. > Also str...

On Thu, Jun 4, 2015 at 5:33 PM, Reid Kleckner <rnk at google.com> wrote: > On Thu, Jun 4, 2015 at 5:17 PM, Teresa Johnson <tejohnson at google.com> wrote: >> >> Agreed. Although I assume you mean invoke the new pass under a >> ThinLTO-only option so that avail extern are not dropped in the >> compile pass before the LTO link? > > > No, this pass

On Thu, Jun 4, 2015 at 3:58 PM, Duncan P. N. Exon Smith < dexonsmith at apple.com> wrote: > > > Personally, I think the right approach is to add a bool to > createGlobalDCEPass defaulting to true named something like > IsAfterInlining. In most standard pass pipelines, GlobalDCE runs after > inlining for obvious reasons, so the default makes sense. The special case > is

...uot;>, Group<f_Group>; def flto_EQ : Joined<["-"], "flto=">, Group<clang_ignored_gcc_optimization_f_Group>; -def flto : Flag<["-"], "flto">, Group<f_Group>; +def flto : Flag<["-"], "flto">, Flags<[CC1Option]>, Group<f_Group>; def fno_lto : Flag<["-"], "fno-lto">, Group<f_Group>; def fmacro_backtrace_limit_EQ : Joined<["-"], "fmacro-backtrace-limit=">, Group<f_Group>, Flags<[DriverOption, Core...

...locations). > > This will require some decoupling between the Clang driver and > frontend (currently Clang's Options.td contains various driver > options that are marked as also being options for Clang's -cc1 > mode; duplicating those in CC1Options.td is probably acceptable, > if we're going to split the driver and frontend into two > different projects), and some shared support code (eg, clang's > sanitizers list) will presumably end up in the driver, because > we don't want a driver -...

*TL;DR* We propose some non-trivial refactoring in Clang and LLVM to enable further work on Flang driver. *SUMMARY* We would like to start extracting the driver/frontend code from Clang (alongside the code that the driver/frontend depends on, e.g. Diagnostics) and move the components that could be re-used by non-C-based languages to LLVM. From our initial investigation we see that these

> ... math errno ... I wouldn't recommend to anyone that they should rely on math errno (because I don't trust libraries to correctly support it). My goal here was to incorporate our existing support for it into the rest of what I'm trying to document. My understanding is that for clang this primarily controls whether or not we feel free to substitute intrinsics for recognized

...g<["-"], "fno-safe-stack">, Group<f_Group>, + HelpText<"Disable safe stack protection against stack-based memory corruption errors">; def fstandalone_debug : Flag<["-"], "fstandalone-debug">, Group<f_Group>, Flags<[CC1Option]>, HelpText<"Emit full debug info for all types used by the program">; def fno_standalone_debug : Flag<["-"], "fno-standalone-debug">, Group<f_Group>, Flags<[CC1Option]>, diff --git a/lib/CodeGen/CodeGenModule.cpp b/lib/CodeGen/CodeGenMod...