search for: z7

On Tue, Nov 19, 2013 at 10:42 AM, Timur Iskhodzhanov <timurrrr at google.com>wrote: > > 2013/11/19 Reid Kleckner <rnk at google.com>: > > I'd just use /Z7, since that's the cl.exe flag for the compatible format. > > This will need a long-form clang -cc1 flag name, though. > > Z7 implies a much more complete debug info than what we'll emit short-term. > Since Z7 is not widely used, I don't think threading Z7 is any simpler &...

...xls-nord-01 J w 0 0,024078979 0 0 bxls-sud-01 J w 0 0 0 0 brux-nord-04 A w 0 0 0 0 brux-sud-04 A w 0 0 0 0 br-nord-07 Ju w 0 0 0 0 br-sud-07 Ju w 0 0 0 0 b-nord-10 O w 0 0 0 0 bsud-10 O w 0,107836089 0 0,107836089 0,035945363 Z1-01 J u 0 0 0 0,040567951 Z3-01 J u 0 0 0 0 Z5-01 J d 0,023116043 0 0 0 Z7-01 J d 0,014130281 0 0 0 Z9-01 J d 0 0 0 0 Z10-01 J d 0 0 0 0 Z12-01 J d 0 0 0 0 Z1-04 A u 0 0 0 0 Z3-04 A u 0 0 0 0 Z5-04 A d 0 0 0 0 Z7-04 A d 0 0 0 0 Z9-04 A d 0 0,013839873 0 0 Z10-04 A d 0 0 0 0 Z12-04 A d 0 0 0 0 Z1-07 Ju u 0 0 0 0 Z3-07 Ju u 0 0 0 0 Z5-07 Ju d 0 0 0 0 Z7-07 Ju d 0 0 0 0 Z9-0...

...I don't think this is the case for Dwarf&CodeView [yet?]. > -Zmlt makes sense as the clang-cl name, or just > make it whatever the debug mode flag is for cl.exe - this is at least > a start down that path. 2013/11/19 Reid Kleckner <rnk at google.com>: > I'd just use /Z7, since that's the cl.exe flag for the compatible format. > This will need a long-form clang -cc1 flag name, though. Z7 implies a much more complete debug info than what we'll emit short-term. Since Z7 is not widely used, I don't think threading Z7 is any simpler than Zmlt. I don'...

.... > > > >> -Zmlt makes sense as the clang-cl name, or just > >> make it whatever the debug mode flag is for cl.exe - this is at least > >> a start down that path. > > > > 2013/11/19 Reid Kleckner <rnk at google.com>: > >> I'd just use /Z7, since that's the cl.exe flag for the compatible > format. > >> This will need a long-form clang -cc1 flag name, though. > > > > Z7 implies a much more complete debug info than what we'll emit > short-term. > > Since Z7 is not widely used, I don't think...

...<-as.formula(paste("LogY ~ WYear + (1+WYear|Site) + (1|", paste(paste(Zs,collapse="+"), ")"))) fit2.4a<-lmer(Trendformula, data = testsamp) which, for mb=8, expands to: fit1<-lmer(LogY ~ WYear + (1 | Site) + (1 | Year) + (1 | Z1+ Z2 + Z3 + Z4 + Z5 + Z6 + Z7 + Z8), data = testsamp) I have no problems with this. However, if the set of random effects has a dimension of 30, then the lmer call is: fit2<-lmer(LogY ~ WYear + (1 | Site) + (1 | Year) + (1 | Z1+Z2 + Z3 + Z4 + Z5 + Z6 + Z7 + Z8 + Z9 + Z10 + Z11 + Z12 + Z13 + Z14 + Z15 + Z16 + Z17 + Z1...

...;> -Zmlt makes sense as the clang-cl name, or just >> >> make it whatever the debug mode flag is for cl.exe - this is at least >> >> a start down that path. >> > >> > 2013/11/19 Reid Kleckner <rnk at google.com>: >> >> I'd just use /Z7, since that's the cl.exe flag for the compatible >> >> format. >> >> This will need a long-form clang -cc1 flag name, though. >> > >> > Z7 implies a much more complete debug info than what we'll emit >> > short-term. >> > Since Z7...

Thank you very much,It works! And some Q&A I meet,may help somebody: 1. If zlib build with 32bit,should use MSVC's 'vcvars32.bat'; 2. Add '-Z7' to CXXFLAGS can release *.pdb file for VS2017 'Step Into' debug, such as: CXXFLAGS="-EHsc -Z7"; 3. If Somebody write a demo in VS2017 3.1 change libxapian.a's name to libxapian.lib; 3.2 make sure the Runtime Library is /MT, can change it at project property page, C/C++...

..."it" worked? I had install mingw earlier, but not set it to $PATH, so must be 'LD=link' and your previous advices on "CXXFLAGS" . I execute configure like this: ./configure LD=link CC="cl -nologo" CXX="$PWD/compile cl -nologo" CXXFLAGS="-EHsc -Z7" AR=lib CPPFLAGS=-IC:/zlib-1.2.3-lib/include LDFLAGS="-LC:/zlib-1.2.3-lib/lib" --prefix="C:/xapian-install" >> 3.1 change libxapian.a's name to libxapian.lib; And sorry,I check again, '3.1 change libxapian.a's name to libxapian.lib;' is not necessary...

...case for Dwarf&CodeView [yet?]. > >> -Zmlt makes sense as the clang-cl name, or just >> make it whatever the debug mode flag is for cl.exe - this is at least >> a start down that path. > > 2013/11/19 Reid Kleckner <rnk at google.com>: >> I'd just use /Z7, since that's the cl.exe flag for the compatible format. >> This will need a long-form clang -cc1 flag name, though. > > Z7 implies a much more complete debug info than what we'll emit short-term. > Since Z7 is not widely used, I don't think threading Z7 is any simpler &g...

That's good news. For having debug info, you could try adding /Z7 on the cmake cmd-line, such as -DCMAKE_CXX_FLAGS="/Z7". Or use the 'RelWithDebInfo' target instead of 'Release' and add -DCMAKE_CXX_FLAGS="/Ob2" (because that target uses /Ob1 as a default). Can you please send a patch on Phabricator if you fix the LLVM_ENABLE_P...

...PDB=true -DLLVM_ENABLE_PROJECTS=lld ../llvm but it seems like the generator overrides it. ps: Created a phabricator account On Mon, Feb 25, 2019 at 2:48 PM Alexandre Ganea <alexandre.ganea at ubisoft.com> wrote: > > That's good news. For having debug info, you could try adding /Z7 on the cmake cmd-line, such as -DCMAKE_CXX_FLAGS="/Z7". Or use the 'RelWithDebInfo' target instead of 'Release' and add -DCMAKE_CXX_FLAGS="/Ob2" (because that target uses /Ob1 as a default). > > Can you please send a patch on Phabricator if you fix the LLVM...

...nfused. > This probably has to do with the fact that most types are duplicates. If there is a class Foo in a header file, and you include that header file in 100 different translation units, all 100 of them of them will get full type information for that class in its object file. This is the /Z7 semantics that clang-cl implements. The alternative is /Zi which uses a type server (out of process de-duplicater) to do this merging at compile time, which is what cl uses by default, and which clang-cl doesn't support. -------------- next part -------------- An HTML attachment was scrubbed.....

...ike the generator overrides it. >> >> >> ps: Created a phabricator account >> >> On Mon, Feb 25, 2019 at 2:48 PM Alexandre Ganea <alexandre.ganea at ubisoft.com> wrote: >> > >> > That's good news. For having debug info, you could try adding /Z7 on the cmake cmd-line, such as -DCMAKE_CXX_FLAGS="/Z7". Or use the 'RelWithDebInfo' target instead of 'Release' and add -DCMAKE_CXX_FLAGS="/Ob2" (because that target uses /Ob1 as a default). >> > >> > Can you please send a patch on Phabricator i...

...>> static int x = 0; >>> void b(int); >>> void a(int) { >>> if (x) >>> b(x); >>> } >>> int main(int argc, char **argv) { >>> a(argc); >>> return x; >>> } >>> >>> >>> clang-cl /Z7 /c a.cpp /Foa.noghash.obj >>> clang-cl /Z7 /c a.cpp -mllvm -emit-codeview-ghash-section >>> /Foa.ghash.good.obj >>> llvm-objcopy a.noghash.obj a.ghash.bad.obj >>> obj2yaml a.ghash.good.obj > a.ghash.good.yaml >>> obj2yaml a.ghash.bad.obj > a.ghash....

...b(int); >>>> void a(int) { >>>> if (x) >>>> b(x); >>>> } >>>> int main(int argc, char **argv) { >>>> a(argc); >>>> return x; >>>> } >>>> >>>> >>>> clang-cl /Z7 /c a.cpp /Foa.noghash.obj >>>> clang-cl /Z7 /c a.cpp -mllvm -emit-codeview-ghash-section >>>> /Foa.ghash.good.obj >>>> llvm-objcopy a.noghash.obj a.ghash.bad.obj >>>> obj2yaml a.ghash.good.obj > a.ghash.good.yaml >>>> obj2yaml a.ghash.b...

...ctually support CV in COFF, then it's just a >> matter of writing CV to the objects, and using the MS linker to link and >> produce the PDB file? >> >> > Their are a couple of options available that allow you to embed debug info > directly into an object file. The /Z7 (enable old-style debug info) option > does not produce a separate PDB file, presumably this generates CodeView 7 > information directly into the object file. The /Yd appears to embed > addition information into the object file along with generating a program > database, but it gives th...

...; >> > >> > >> ps: Created a phabricator account > >> > >> On Mon, Feb 25, 2019 at 2:48 PM Alexandre Ganea <alexandre.ganea at ubisoft.com> wrote: > >> > > >> > That's good news. For having debug info, you could try adding /Z7 on the cmake cmd-line, such as -DCMAKE_CXX_FLAGS="/Z7". Or use the 'RelWithDebInfo' target instead of 'Release' and add -DCMAKE_CXX_FLAGS="/Ob2" (because that target uses /Ob1 as a default). > >> > > >> > Can you please send a patch on Pha...

...n inside of addObjectsToPDB Is anyone working on those? Also has anyone thought about merging .obj files to deduplicate type infomation so we can do the linking on projects to generate something like a lib file, but deduplicated debug information (as far as I know actual .lib just put all pdbs or /Z7 debug info inside a file without dedup). Just looking at the code it seems it is much more mature and also the choice of SHA1_8 seems interesting (still don't know why not use xxHash64). ps: My code to add ghashes to msvc compiled .obj files is almost ready to be pushed as an option for llvm-...

...> >> ps: Created a phabricator account >> >> On Mon, Feb 25, 2019 at 2:48 PM Alexandre Ganea <alexandre.ganea at ubisoft.com<mailto:alexandre.ganea at ubisoft.com>> wrote: >> > >> > That's good news. For having debug info, you could try adding /Z7 on the cmake cmd-line, such as -DCMAKE_CXX_FLAGS="/Z7". Or use the 'RelWithDebInfo' target instead of 'Release' and add -DCMAKE_CXX_FLAGS="/Ob2" (because that target uses /Ob1 as a default). >> > >> > Can you please send a patch on Phabricator i...

...5T*4&%T:#TO;6YT+W=I M;E]C+W=I;F1O=W,O=&5M<`I4>7!E/6AD"DQA8F5L/51M<"!$<FEV90I&:6QE M<WES=&5M/7=I;CDU"@I;1')I=F4@1ET*4&%T:#TD>TA/345]"E1Y<&4];F5T M=V]R:PI,86)E;#U(;VUE"D9I;&5S>7-T96T]=VEN.34*"EMW:6YE70I7:6YD M;W=S/6,Z7'=I;F1O=W,*4WES=&5M/6,Z7'=I;F1O=W-<<WES=&5M"E1E;7`] M93I<"E!A=&@]8SI<=VEN9&]W<SMC.EQW:6YD;W=S7'-Y<W1E;3ME.EP[9CI< M"D=R87!H:6-S1')I=F5R/7@Q,61R=@IP<FEN=&5R/6]F9@H*6W@Q,61R=ET* M06QL;V-3>7-T96U#;VQO<G,@/2`Q,#`*4')I=F...