mersenneforum.org  

Go Back   mersenneforum.org > Factoring Projects > YAFU

Reply
 
Thread Tools
Old 2015-07-01, 13:44   #1
queremendi
 
Jul 2015

12 Posts
Default Using YAFU in Visual Studio

Hello everyone!
I am currently working in a project where I have to implement a plug-in that factorizes numbers. My intention is to use, within others, the NFS algorithm. I read in the README file that there are Build files available for MS Visual Studio Express.

Does anyone have an idea of how can I use the NFS implementation from Visual Studio?

Thank you!
Queremendi
queremendi is offline   Reply With Quote
Old 2015-07-02, 00:57   #2
jasonp
Tribal Bullet
 
jasonp's Avatar
 
Oct 2004

67228 Posts
Default

By far the easiest option is to call the YAFU binary and parse its results. Building from source requires compiling several other libraries, most of which don't have MSVC2008 build files anymore
jasonp is offline   Reply With Quote
Old 2015-07-04, 15:55   #3
Brian Gladman
 
Brian Gladman's Avatar
 
May 2008
Worcester, United Kingdom

10000011102 Posts
Default

Quote:
Originally Posted by jasonp View Post
By far the easiest option is to call the YAFU binary and parse its results. Building from source requires compiling several other libraries, most of which don't have MSVC2008 build files anymore
Although the SVN version of YAFU doesn't currently build with Visual Studio, when I asked Ben if he intended to drop this build option, his answer was 'no' - i.e. he hoped to update the code to get Visual Studio builds working again.

But I must admit this was some time ago and, although I have been monitoring the SVN for updates that will get the Visual Studio build working again, it has not changed in months.

As I am keen to get YAFU working with Visual Studio 2015, maybe Ben can provide an update on the current situation?

Although I am aware that sections of YAFU code don't compile with the Microsoft x64 compiler, I was not aware of third party library dependencies that prevent this build. Could you elaborate please?
Brian Gladman is offline   Reply With Quote
Old 2015-07-05, 04:31   #4
bsquared
 
bsquared's Avatar
 
"Ben"
Feb 2007

2·32·191 Posts
Default

Quote:
Originally Posted by Brian Gladman View Post
Although the SVN version of YAFU doesn't currently build with Visual Studio, when I asked Ben if he intended to drop this build option, his answer was 'no' - i.e. he hoped to update the code to get Visual Studio builds working again.

But I must admit this was some time ago and, although I have been monitoring the SVN for updates that will get the Visual Studio build working again, it has not changed in months.

As I am keen to get YAFU working with Visual Studio 2015, maybe Ben can provide an update on the current situation?

Although I am aware that sections of YAFU code don't compile with the Microsoft x64 compiler, I was not aware of third party library dependencies that prevent this build. Could you elaborate please?
I have been working on a different project for a while now and haven't made time for yafu updates. But it is still my plan to get the visual studio builds fully working and a new version released. Just can't say when it will happen exactly.
bsquared is offline   Reply With Quote
Old 2015-07-05, 08:14   #5
Brian Gladman
 
Brian Gladman's Avatar
 
May 2008
Worcester, United Kingdom

2·263 Posts
Default

Thanks Ben, I am willing to help if an extra 'pair of hands' would speed things up.
Brian Gladman is offline   Reply With Quote
Old 2015-07-07, 16:30   #6
jasonp
Tribal Bullet
 
jasonp's Avatar
 
Oct 2004

DD216 Posts
Default

Quote:
Originally Posted by Brian Gladman View Post
Although I am aware that sections of YAFU code don't compile with the Microsoft x64 compiler, I was not aware of third party library dependencies that prevent this build. Could you elaborate please?
My understanding is that support for MSVC2008 in GMP-ECM and Msieve was discontinued, so that a more recent version of the tools is required to build those dependencies.
jasonp is offline   Reply With Quote
Old 2015-07-08, 11:45   #7
henryzz
Just call me Henry
 
henryzz's Avatar
 
"David"
Sep 2007
Cambridge (GMT/BST)

2·5·587 Posts
Default

IMO msieve shouldn't drop any visual studio versions due to the gpu version only supporting certain versions of visual studio/CUDA.
henryzz is online now   Reply With Quote
Old 2015-07-08, 14:16   #8
Brian Gladman
 
Brian Gladman's Avatar
 
May 2008
Worcester, United Kingdom

2·263 Posts
Default

I only fully support the last version of Visual Studio to be released, which means 2013 at the moment. But I will support Visual Studio 2013 and 2015 at least until Intel and NVIDIA add support for the latter. I am certainly not maintaining Visual Studio builds for any versions older than 2012.
Brian Gladman is offline   Reply With Quote
Old 2015-07-08, 16:15   #9
henryzz
Just call me Henry
 
henryzz's Avatar
 
"David"
Sep 2007
Cambridge (GMT/BST)

2×5×587 Posts
Default

Intel and Nvidia aren't the problem. There is a bug in the library that msieve uses that stops it working past a certain cuda version. My memory is that vs2012 is the latest that that cuda version will work with.
My vs2012 installation is completely messed up inreversively. I don't think I could get it to compile with vs2013.
I will confirm the numbers when I get home.
As long as you can compile and run a version of the GPU version that is fine.
Later versions of cuda will compile than work.
If you have a working build system set up for it I would appreciate a version that works on a core2.
I will investigate the situation with vs2013 again tonight.
henryzz is online now   Reply With Quote
Old 2015-07-08, 17:12   #10
henryzz
Just call me Henry
 
henryzz's Avatar
 
"David"
Sep 2007
Cambridge (GMT/BST)

16EE16 Posts
Default

Quote:
Originally Posted by henryzz View Post
Intel and Nvidia aren't the problem. There is a bug in the library that msieve uses that stops it working past a certain cuda version. My memory is that vs2012 is the latest that that cuda version will work with.
My vs2012 installation is completely messed up inreversively. I don't think I could get it to compile with vs2013.
I will confirm the numbers when I get home.
As long as you can compile and run a version of the GPU version that is fine.
Later versions of cuda will compile than work.
If you have a working build system set up for it I would appreciate a version that works on a core2.
I will investigate the situation with vs2013 again tonight.
http://mersenneforum.org/showthread.php?t=19615 states that the latest version of cuda to work is 5.5. https://devtalk.nvidia.com/default/t...l-studio-2013/ states that vs2013 support is added only in 6.0. Hence we need vs2012 support.
The binary in the above thread used instructions beyond what my core2 will cope with(I assume within gmp/mpir).
henryzz is online now   Reply With Quote
Old 2015-07-09, 15:20   #11
Brian Gladman
 
Brian Gladman's Avatar
 
May 2008
Worcester, United Kingdom

52610 Posts
Default

Cuda 7.0 supports Visual Studio 2013 running on x64. Are there any more details of the library bug that causes the problem with Cuda versions after 5.5?
Brian Gladman is offline   Reply With Quote
Reply

Thread Tools


Similar Threads
Thread Thread Starter Forum Replies Last Post
Building GMP-ECM with Visual Studio 2017 Brian Gladman GMP-ECM 16 2017-11-06 16:44
Visual Studio 2015 build Brian Gladman Msieve 3 2016-10-04 10:40
GMP-ECM with Visual Studio 2015 Brian Gladman GMP-ECM 0 2016-09-29 11:33
Visual Studio (yech) R.D. Silverman Programming 12 2015-09-07 00:54
AMD64 Applications with Visual Studio 6 or .Net Ethan (EO) Software 0 2004-08-09 04:07

All times are UTC. The time now is 20:48.

Wed May 12 20:48:59 UTC 2021 up 34 days, 15:29, 1 user, load averages: 2.17, 2.01, 2.08

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, Jelsoft Enterprises Ltd.

This forum has received and complied with 0 (zero) government requests for information.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.
A copy of the license is included in the FAQ.