search for: linkonce_odr_auto_hide

...O doesn't deal with globals that has linkonce_odr and unnamed_addr (for macho at least) because it prohibits the autohide optimization during link time. In LLVM, we tagged a global linkonce_odr and unnamed_addr to indicate to the linker can hide them from symbol table if they were picked (aka, linkonce_odr_auto_hide linkage). It is very commonly used for some type of Tables for c++ code in clang for example. However, thinLTO is promoting these symbols to weak_odr + unnamed_addr, which lose the property. As a result, it introduces unnecessary weak external symbols and weak external are not good for performance...

...ls that has > linkonce_odr and unnamed_addr (for macho at least) because it prohibits the > autohide optimization during link time. > > In LLVM, we tagged a global linkonce_odr and unnamed_addr to indicate to > the linker can hide them from symbol table if they were picked (aka, > linkonce_odr_auto_hide linkage). It is very commonly used for some type of > Tables for c++ code in clang for example. > However, thinLTO is promoting these symbols to weak_odr + unnamed_addr, > which lose the property. As a result, it introduces unnecessary weak > external symbols and weak external are not g...

...konce_odr and unnamed_addr (for macho at least) because it prohibits the >> autohide optimization during link time. >> >> In LLVM, we tagged a global linkonce_odr and unnamed_addr to indicate to >> the linker can hide them from symbol table if they were picked (aka, >> linkonce_odr_auto_hide linkage). It is very commonly used for some type of >> Tables for c++ code in clang for example. >> However, thinLTO is promoting these symbols to weak_odr + unnamed_addr, >> which lose the property. As a result, it introduces unnecessary weak >> external symbols and weak ex...

...ls that has > linkonce_odr and unnamed_addr (for macho at least) because it prohibits the > autohide optimization during link time. > > In LLVM, we tagged a global linkonce_odr and unnamed_addr to indicate to > the linker can hide them from symbol table if they were picked (aka, > linkonce_odr_auto_hide linkage). It is very commonly used for some type of > Tables for c++ code in clang for example. > However, thinLTO is promoting these symbols to weak_odr + unnamed_addr, > which lose the property. As a result, it introduces unnecessary weak > external symbols and weak external are not g...

...9;t deal with globals that has linkonce_odr and unnamed_addr (for macho at least) because it prohibits the autohide optimization during link time. > > In LLVM, we tagged a global linkonce_odr and unnamed_addr to indicate to the linker can hide them from symbol table if they were picked (aka, linkonce_odr_auto_hide linkage). It is very commonly used for some type of Tables for c++ code in clang for example. > However, thinLTO is promoting these symbols to weak_odr + unnamed_addr, which lose the property. As a result, it introduces unnecessary weak external symbols and weak external are not good for perform...

...9;t deal with globals that has linkonce_odr and unnamed_addr (for macho at least) because it prohibits the autohide optimization during link time. > > In LLVM, we tagged a global linkonce_odr and unnamed_addr to indicate to the linker can hide them from symbol table if they were picked (aka, linkonce_odr_auto_hide linkage). It is very commonly used for some type of Tables for c++ code in clang for example. > However, thinLTO is promoting these symbols to weak_odr + unnamed_addr, which lose the property. As a result, it introduces unnecessary weak external symbols and weak external are not good for perform...

...d_addr (for macho at least) because it prohibits the >>> autohide optimization during link time. >>> >>> In LLVM, we tagged a global linkonce_odr and unnamed_addr to indicate to >>> the linker can hide them from symbol table if they were picked (aka, >>> linkonce_odr_auto_hide linkage). It is very commonly used for some type of >>> Tables for c++ code in clang for example. >>> However, thinLTO is promoting these symbols to weak_odr + unnamed_addr, >>> which lose the property. As a result, it introduces unnecessary weak >>> external sym...

...konce_odr and unnamed_addr (for macho at least) because it prohibits the >> autohide optimization during link time. >> >> In LLVM, we tagged a global linkonce_odr and unnamed_addr to indicate to >> the linker can hide them from symbol table if they were picked (aka, >> linkonce_odr_auto_hide linkage). It is very commonly used for some type of >> Tables for c++ code in clang for example. >> However, thinLTO is promoting these symbols to weak_odr + unnamed_addr, >> which lose the property. As a result, it introduces unnecessary weak >> external symbols and weak ex...

>> The days of the old .ll parser are long gone, but is it too late to >> change? In case it is not, the attached patches implement just that >> :-) > I'm afraid you need to provide syntax autoupgrade until 4.0 Why, we moved to doing autoupgrade via bitcode quiet some time ago. There were quiet a few format changes to the .ll in the process. Cheers, Rafael

...with globals that has linkonce_odr and unnamed_addr (for macho at least) because it prohibits the autohide optimization during link time. >> >> In LLVM, we tagged a global linkonce_odr and unnamed_addr to indicate to the linker can hide them from symbol table if they were picked (aka, linkonce_odr_auto_hide linkage). It is very commonly used for some type of Tables for c++ code in clang for example. >> However, thinLTO is promoting these symbols to weak_odr + unnamed_addr, which lose the property. As a result, it introduces unnecessary weak external symbols and weak external are not good for per...

...least) because it prohibits the >>>> autohide optimization during link time. >>>> >>>> In LLVM, we tagged a global linkonce_odr and unnamed_addr to indicate >>>> to the linker can hide them from symbol table if they were picked (aka, >>>> linkonce_odr_auto_hide linkage). It is very commonly used for some type of >>>> Tables for c++ code in clang for example. >>>> However, thinLTO is promoting these symbols to weak_odr + unnamed_addr, >>>> which lose the property. As a result, it introduces unnecessary weak >>>&...

...rohibits the >>>>> autohide optimization during link time. >>>>> >>>>> In LLVM, we tagged a global linkonce_odr and unnamed_addr to indicate >>>>> to the linker can hide them from symbol table if they were picked (aka, >>>>> linkonce_odr_auto_hide linkage). It is very commonly used for some type of >>>>> Tables for c++ code in clang for example. >>>>> However, thinLTO is promoting these symbols to weak_odr + >>>>> unnamed_addr, which lose the property. As a result, it introduces >>>>&g...

...obals that has linkonce_odr and unnamed_addr (for macho at least) because it prohibits the autohide optimization during link time. >>> >>> In LLVM, we tagged a global linkonce_odr and unnamed_addr to indicate to the linker can hide them from symbol table if they were picked (aka, linkonce_odr_auto_hide linkage). It is very commonly used for some type of Tables for c++ code in clang for example. >>> However, thinLTO is promoting these symbols to weak_odr + unnamed_addr, which lose the property. As a result, it introduces unnecessary weak external symbols and weak external are not good for...

...d_addr (for macho at least) because it prohibits the >>> autohide optimization during link time. >>> >>> In LLVM, we tagged a global linkonce_odr and unnamed_addr to indicate to >>> the linker can hide them from symbol table if they were picked (aka, >>> linkonce_odr_auto_hide linkage). It is very commonly used for some type of >>> Tables for c++ code in clang for example. >>> However, thinLTO is promoting these symbols to weak_odr + unnamed_addr, >>> which lose the property. As a result, it introduces unnecessary weak >>> external sym...

...;>>>> autohide optimization during link time. >>>>>> >>>>>> In LLVM, we tagged a global linkonce_odr and unnamed_addr to indicate >>>>>> to the linker can hide them from symbol table if they were picked (aka, >>>>>> linkonce_odr_auto_hide linkage). It is very commonly used for some type of >>>>>> Tables for c++ code in clang for example. >>>>>> However, thinLTO is promoting these symbols to weak_odr + >>>>>> unnamed_addr, which lose the property. As a result, it introduces >&g...

...at has linkonce_odr and unnamed_addr (for macho at least) because it prohibits the autohide optimization during link time. >>>> >>>> In LLVM, we tagged a global linkonce_odr and unnamed_addr to indicate to the linker can hide them from symbol table if they were picked (aka, linkonce_odr_auto_hide linkage). It is very commonly used for some type of Tables for c++ code in clang for example. >>>> However, thinLTO is promoting these symbols to weak_odr + unnamed_addr, which lose the property. As a result, it introduces unnecessary weak external symbols and weak external are not good...

...inkonce_odr and unnamed_addr (for macho at least) because it prohibits the autohide optimization during link time. >>>>> >>>>> In LLVM, we tagged a global linkonce_odr and unnamed_addr to indicate to the linker can hide them from symbol table if they were picked (aka, linkonce_odr_auto_hide linkage). It is very commonly used for some type of Tables for c++ code in clang for example. >>>>> However, thinLTO is promoting these symbols to weak_odr + unnamed_addr, which lose the property. As a result, it introduces unnecessary weak external symbols and weak external are not...

...; autohide optimization during link time. >>>>>>> >>>>>>> In LLVM, we tagged a global linkonce_odr and unnamed_addr to >>>>>>> indicate to the linker can hide them from symbol table if they were picked >>>>>>> (aka, linkonce_odr_auto_hide linkage). It is very commonly used for some >>>>>>> type of Tables for c++ code in clang for example. >>>>>>> However, thinLTO is promoting these symbols to weak_odr + >>>>>>> unnamed_addr, which lose the property. As a result, it intro...

...ization during link time. >>>>>>>> >>>>>>>> In LLVM, we tagged a global linkonce_odr and unnamed_addr to >>>>>>>> indicate to the linker can hide them from symbol table if they were picked >>>>>>>> (aka, linkonce_odr_auto_hide linkage). It is very commonly used for some >>>>>>>> type of Tables for c++ code in clang for example. >>>>>>>> However, thinLTO is promoting these symbols to weak_odr + >>>>>>>> unnamed_addr, which lose the property. As a resu...

...odr and unnamed_addr (for macho at least) because it prohibits the autohide optimization during link time. >>>>>> >>>>>> In LLVM, we tagged a global linkonce_odr and unnamed_addr to indicate to the linker can hide them from symbol table if they were picked (aka, linkonce_odr_auto_hide linkage). It is very commonly used for some type of Tables for c++ code in clang for example. >>>>>> However, thinLTO is promoting these symbols to weak_odr + unnamed_addr, which lose the property. As a result, it introduces unnecessary weak external symbols and weak external are...