On 02/05/2019 10:44, degski wrote: > On Thu, 2 May 2019 at 08:30, Cactus <rieman...@gmail.com > <mailto:rieman...@gmail.com>> wrote: > > Unfortunately I am away at the moment so I am a bit limited in what > I can do to help until Tuesday next week. I have tried the > broadwell_avx build and it does produce errors for me as well, but > oddly, not the error you are seeing. > > > I was tracking my problem in/with the basic broadwell build, that one > works. The broadwell_avx gives (a.o.): > > 1> Assembling and_n.asm ==> x64\Debug\and_n.obj > 1> ..\..\..\mpn\x86_64w\broadwell\avx\and_n.asm(117): error : undefined > symbol `SizeB' (first use) > 1> ..\..\..\mpn\x86_64w\broadwell\avx\and_n.asm(117): error : (Each > undefined symbol is reported only once.) > 1> ..\..\..\mpn\x86_64w\broadwell\avx\and_n.asm(152): error : undefined > symbol `CountB' (first use) > 1> Y:\REPOS\mpir\msvc\vsyasm.targets(81,5): error MSB3721: The command > ""C:\Program Files\yasm\"vsyasm.exe -Xvc -f x64 -g cv8 -i > "..\..\..\mpn\x86_64w\\" -o "..\..\..\mpn\and_n.obj" -rnasm -pnasm > ..\..\..\mpn\x86_64w\broadwell\avx\and_n.asm" exited with code 1. > > Which seem more like coding issues. > > I guess that's what you were looking at. Next week [or whenever you get > to it] no problem.
Yes, there were errors in three of the Windows x64 assembler code files for broadwell_avx. I have just corrected these in the repository and the build should now succeed and pass the tests. Brian -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to mpir-devel+unsubscr...@googlegroups.com. To post to this group, send email to mpir-devel@googlegroups.com. Visit this group at https://groups.google.com/group/mpir-devel. For more options, visit https://groups.google.com/d/optout.
