search for: moduleintattrs

...are parsed and used by the backend passes: 1. Tools such as clang and llc call cl::ParseCommandLineOptions. Any of the options that should be written to the bitcode as function or module attributes (these options are declared as CodeGenOpt, which is a subclass of cl::opt) are saved to Function or ModuleIntAttrs in CodeGenOptions.cpp. 2. setFunctionAttribute is called to move the function and module options saved in step 1 to the bitcode. Also, options stored in TargetOptions are moved to the bitcode too. Pre-existing attributes in the bitcode are overwritten by the options in the command line. 3. The back...

...>> >> 1. Tools such as clang and llc call cl::ParseCommandLineOptions. Any of >> the options that should be written to the bitcode as function or module >> attributes (these options are declared as CodeGenOpt, which is a subclass >> of cl::opt) are saved to Function or ModuleIntAttrs in CodeGenOptions.cpp. >> 2. setFunctionAttribute is called to move the function and module options >> saved in step 1 to the bitcode. Also, options stored in TargetOptions are >> moved to the bitcode too. Pre-existing attributes in the bitcode are >> overwritten by the opti...

...d and used by the backend passes: > > 1. Tools such as clang and llc call cl::ParseCommandLineOptions. Any of the options that should be written to the bitcode as function or module attributes (these options are declared as CodeGenOpt, which is a subclass of cl::opt) are saved to Function or ModuleIntAttrs in CodeGenOptions.cpp. > 2. setFunctionAttribute is called to move the function and module options saved in step 1 to the bitcode. Also, options stored in TargetOptions are moved to the bitcode too. Pre-existing attributes in the bitcode are overwritten by the options in the command line. >...

...ed by the backend passes: >> >> 1. Tools such as clang and llc call cl::ParseCommandLineOptions. Any of the options that should be written to the bitcode as function or module attributes (these options are declared as CodeGenOpt, which is a subclass of cl::opt) are saved to Function or ModuleIntAttrs in CodeGenOptions.cpp. >> 2. setFunctionAttribute is called to move the function and module options saved in step 1 to the bitcode. Also, options stored in TargetOptions are moved to the bitcode too. Pre-existing attributes in the bitcode are overwritten by the options in the command line. &...

...call cl::ParseCommandLineOptions. Any >>>>>> of the options that should be written to the bitcode as function or module >>>>>> attributes (these options are declared as CodeGenOpt, which is a subclass >>>>>> of cl::opt) are saved to Function or ModuleIntAttrs in CodeGenOptions.cpp. >>>>>> 2. setFunctionAttribute is called to move the function and module >>>>>> options saved in step 1 to the bitcode. Also, options stored in >>>>>> TargetOptions are moved to the bitcode too. Pre-existing attributes in...

...neOptions. >>>>>>>> Any of the options that should be written to the bitcode as function or >>>>>>>> module attributes (these options are declared as CodeGenOpt, which is a >>>>>>>> subclass of cl::opt) are saved to Function or ModuleIntAttrs in >>>>>>>> CodeGenOptions.cpp. >>>>>>>> 2. setFunctionAttribute is called to move the function and module >>>>>>>> options saved in step 1 to the bitcode. Also, options stored in >>>>>>>> TargetOptions...

...gt;>>>>>> Any of the options that should be written to the bitcode as function or >>>>>>>>>> module attributes (these options are declared as CodeGenOpt, which is a >>>>>>>>>> subclass of cl::opt) are saved to Function or ModuleIntAttrs in >>>>>>>>>> CodeGenOptions.cpp. >>>>>>>>>> 2. setFunctionAttribute is called to move the function and module >>>>>>>>>> options saved in step 1 to the bitcode. Also, options stored in >>>>>&gt...

> On Nov 14, 2014, at 2:44 PM, Duncan P. N. Exon Smith <dexonsmith at apple.com> wrote: > > +chrisb > >> On 2014-Nov-13, at 16:33, Akira Hatanaka <ahatanak at gmail.com> wrote: >> >> I'm working on fixing PR21471, which is about embedding codegen command line options into the bitcode as function or module-level attributes so that they don't get