- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
All parameters regarding the placement/naming are still broken in update3, see
http://software.intel.com/en-us/forums/showthread.php?t=78957
which is applicable for all 12.0 releases/updates and is definitely different from the MS C++ behavior.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have escalated the issue of /Fd being ignored as issue DPD200168013.
In the case you describe, the compiler will update vcxx.pdb on the subsequent compilations, so you need only one.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
LINK : fatal error LNK1248: image size (8012AC6B) exceeds maximum allowable size (80000000)
Looks like I'm going to have to split up my static library since it's a bit over 2GB. I didn't realized this was a Windows limit even on x64.
The same static debug library was 1.6 GB using IVF 11.1 so I was getting close anyways.
Thanks again,
Lou
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Actually splitting the static library into two worked fine. When our application is compiled with optimization the static library is around 600 MB, with the following debug options it's 1.6 GB with IVF 11.1 and over 2 GB with IVF 12.0. The "LIB" command failed, not the creating of the executable, e.g. LINK.EXE. I realize that "LIB" inherently calls "LINK.EXE" but I was just doing a "LIB /out:mylib.lib *.obj" Apparently there is a 2 GB static library file size limit. BTW, we don't use large static arrays, we dynamically allocate.
ifort /Zi /Od /fpp /recursive /debug-parameters:all /fpe:0 /names:uppercase /traceback /check:uninit /Qau
to /Qtrapuv /libs:dll /threads /Qopenmp /QaxAVX
Lou
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi: Has this issue been resolved? I tried to make two .lib files today, but they really couldn't live together in the same installation directory because both pdb files were named vc100.pdb. /pdbfile: didn't seem to work, but perhaps there's more to it. (This is third party software so I'm a bit limited in how much I can monkey with their build system.)
Thanks,
Allen
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, this has been resolved by using the /Fd option.
Thanks,
Lou
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Lou: Do you know which release resolved this issue? I have ifort 12.0.1.127 and "ifort /c /debug:full /Fd:example example.f90" still produces a vc100.pdb file.
Thanks,
Allen
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It would be compiler version 12.1, or Compose XE 2011 Update 6. You're using a compiler earlier than the one cited in this thread.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
OK. I updated my windows version to 13.1.0.149 and it works fine. Thank you!
Allen
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page