ed2kers 电驴资源下载站

《高性能Fortran编译器》(PGI Visual Fortran 2010)v11.1.with.VS2010.Shell.X64/含keyfile[压缩包]

《高性能Fortran编译器》(PGI Visual Fortran 2010)v11.1.with.VS2010.Shell.X64/含keyfile[压缩包]
类别:
软件 - 编程开发
状态:
精华资源
摘要:
发行时间: 2011年制作发行: © 2011 STMicroelectronics语言: 英文
发布:
2011-02-09 10:44:50
更新:
2011-02-09 13:52:21

电驴资源

用户共享的电驴资源列表
[高性能Fortran编译器].PGI.Visual.Fortran.2010.v11.1.with.VS2010.Shell.X64-Lz0.zip 551.33 MB
551.33 MB

电驴资源简介

iptcomContents">简介:
IPB Image

引用1) Unpack and install.
2) Place keyfile in program/game directory.
3) Enjoy this release! 软件类型:软件 应用软件
软件性质:破解软件
操作系统:Windows
应用平台:Windows
问题反馈: http://www.pgroup.com/support/index.htm
网站链接: http://www.pgroup.com/
软件介绍:世界领先的独立的高性能计算技术编译器及开发工具供应商Portland Group™(PGI),PGI Visual Fortran™(PVF™)全面上市销售。PVF将 PGI的高性能64位及32位Fortran并行编译器及开发工具套件与Microsoft Visual Studio 2005整合在一起,为科学工作者和工程师从32位升级到64位Microsoft Windows平台提供一套高效的系统开发解决方案。
科研工作者将PGI编译器及开发工具广泛用于内置英特尔和AMD高性能微处理器的 64位和32位 Linux工作站、服务器和集群器上。该版软件使Portland Group对运行在Windows平台上的64位和32位Fortran应用程序的开发支持扩展到英特尔和AMD的64位和32位微处理器,新软件运行在深受市场欢迎的Microsoft Visual Studio 2005集成开发环境(IDE)。PGI Visual Fortran 套件整合了多种兼容性能,使从现有的支持Windows的32位Fortran升级到64位平台变得十分简单,具体兼容功能包括支持Windows 32位应用编程接口(API)、调用规则、汇编命令以及公认的标准实用工具库。
Microsoft Visual Studio是世界上应用最广泛的集成开发环境。Visual Studio 2005工具及技术( 包括一个并行调试器 )使开发人员可以利用他们现有的Windows开发技能及经验开发在Windows Compute Cluster Server 2003平台上运行的HPC(高性能计算)应用程序。
PGI Visual Fortran包括最新版的PGI本机OpenMP,以及支持FORTRAN77和Fortran95编程语言的自动并行化编译器,主要特性包括一整套:
由面向Fortran的文本编辑器、Fortran本征函数提示和选择关键字组成的Visual Studio Fortran项目系统;
Fortran 应用程序自定义创建引擎;
自定义调试引擎,提供Fortran所需的语言专用调试功能;
支持单线程、多线程及OpenMP并行应用程序调试;
兼容Microsoft Visual C++ 2008;
支持调试PGI Fortran和Visual C++ 2005的混合应用程序
PGI的编译器及开发工具都具有如下特性:完全本机支持OpenMP并行编程扩展、在多核心处理器上的自动并行化、完全支持64位寻址、本机集成标量和矢量SSE/SSE2/SSE3代码生成,以及PGI 世界领先的优化基础设施。
PGI Visual Fortran是为64位的AMD64和英特尔的EM64T及32位的x86处理器高度优化的,其创建PGI Unified Binary™的功能是业内独一无二的。PGI Unified Binary™是一个能够在两个处理器平台上运行的可执行文件,内含针对AMD64和EM64T处理器优化的代码序列。PGI Unified Binary使独立软件开发商(ISV)和自定义应用程序开发人员认识到一个64位平台的优点,同时还能充分利用英特尔和AMD公司开带来的最新创新技术。
代码 
  LineZer0! ²   ² ² 
²²² ²     ² ²²  ² ²±
±²²   ²   ²²²² ²²²
² ² ²  ² ² ²²
² ²² ² ²  ²²² ² ²
²² ²² ²  ²²² ²² ² ²
²  ²²² ² ²²²  ²² ±² ²²±
² ²  ²²² ²²² ²²±
² ±² ² ²² ²²²²± ± ²
  ² ²°²  ² ² ²²² ² ±  ²²  
² ² ²²    ² ²²  ²  ² ²
 ²² ² ²²²² ²   ² ² ²² 
²² ²²²  ²  ² ² ²²² ²²± ²²
  ²²² ² ²²²  ²²²  
cpN²²² ±² ²²±±²²²²²°² ²± ²²²cRo
²² ±²²²²² ²²² ²²²²²²²± ²²
²²²² ±±²²²²²  ² ²² ²² ²²²²²±± ²²²²
² ²² ²²²² ²² presents ² ²±²² ²² ²
²² ² ²²  ² ² ²²
²² ²²± ²  ²  ² ±²² ²²
²² °°     °° ²²
² ²
² Visual Fortran 2010 v11.1.with.VS2010.Shell ²
     
²²² Release Date 2011-02-04 ²²²
²² Nfo Date 2011-02-04 ²²
²² ² ² ²²
²  Num. Disks xx/12 OS X64  ²
²  Nfo Time 13 37 Rel Type License  ²
²  Cracker Team Lz0 Archive lz0*.zip  ²
²  Packer Team Lz0 Rating Your choice  ²
²  Supplier Team Lz0 Language English  ²
²  Protection FlexLM  ²
²   ²
²  Requirements N/A  ²
²  Publisher URL http //www.pgroup.com/  ²
²  Publisher PGI  ²
²   ²
²  x Keyfile / License - Emulator  ²
²  - Patch - Serial  ²
²  - Cracked .EXE / .DLL - Retail  ²
²  - Keygen - Trainer  ²
²  ² - Loader - Other ²  ²
² ²   ² ²
²²     ²²
²² ²  1999 - 2011  ² ²²
² ²²  °°° °°°  ²² ²
  ²²² ² ² °±± ²² ±±° ² ² ²²²  
²²²   ² ±²² ²²± ²   ²²²
²²   ²²²² + I N F O + ²²²   ²²
²² ²  ²²²² ²  ² ²²
²   ²
²  PGI Fortran compilers offer world-class performance and  ²
²  features including both automatic and OpenMP 3.0  ²
²  parallelization support for optimizing performance on  ²
²  multi-core processors. State-of-the-art compiler  ²
²  technologies found in PVF include vectorization,  ²
²  parallelization, interprocedural analysis, memory hierarchy  ²
²  optimization, cross file function inlining, CPU-specific  ²
²  optimization and more. PGI Unified Binary? technology  ²
²  streamlines cross-platform support by combining into a  ²
²  single executable file code optimized for any number of  ²
²  different x64 processors.  ²
²   ²
²  PVF augments the Visual Studio debugger by adding a Fortran  ²
²  language specific custom debug engine. The PVF debug engine  ²
²  supports debugging of single and multi-thread, OpenMP,  ²
²  multi-thread MSMPI and hybrid MSMPI+OpenMP Fortran  ²
²  applications. It enables debugging of 64-bit or 32-bit  ²
²  applications using source code or assembly code, and  ²
²  provides full access to the registers and hardware state of  ²
²  the processors. Other multi-process MSMPI capabilities  ²
²  include Visual Studio property pages for configuring  ²
²  compile-time options, launching applications either locally  ²
²  on a workstation or on a distributed-memory Windows HPC  ²
²  Server 2008 cluster system, and debugging of programs  ²
²  running either locally or on a cluster.  ²
²   ²
²  Visual Studio Integration  ²
²  PVF includes features to enable rapid code development. PVF  ²
²  adds syntax coloring, Fortran intrinsics tips and keyword  ²
²  completion to the Visual Studio editor. PVF includes a  ²
²  complete Fortran build environment for Visual Studio with  ²
²  Fortran specific features such as automatic build  ²
²  dependency management. PVF is interoperable with Microsoft  ²
²  Visual C++ so Fortran sub-programs can call C functions and  ²
²  vice versa. PVF includes a number of DVF/CVF compatibility  ²
²  features including full support for the Win32 API. Sample  ²
²  projects include building Fortran dialog boxes, console and  ²
²  Windows applications, DLLs and static libraries.  ²
²   ²
²  PVF augments the Visual Studio debugger with a custom debug  ²
²  engine that provides Fortran language specific debugging  ²
²  capability. The PVF debug engine supports debugging of  ²
²  single-thread, multi-thread, and OpenMP applications. It  ²
²  enables debugging of 64-bit or 32-bit applications using  ²
²  source code or assembly code, and it provides full access  ²
²  to the registers and hardware state of the processor. The  ²
²  PVF debug engine can debug executable files built for  ²
²  native Windows, Windows Subsystem for UNIX-based  ²
²  Applications SUA and Windows Services for UNIX SFU . The  ²
²  PVF debug engine is interoperable with the Visual C++.  ²
²   ²
² ²   ² ²
²²     ²²
² ²²   ²² ²
²  ²²  °°° °°°  ²²  ²
  ²²² ² ² °±± ²² ±±° ² ² ²²²  
²²²   ² ±²² ²²± ²   ²²²
²²   ²²²²+ I N S T A L L +²²²   ²²
²² ²  ²²²² ²  ² ²²
²   ²
²  1 Unpack and install.  ²
²  2 Place keyfile in program/game directory.  ²
²  3 Enjoy this release!  ²
²   ²
² ²   ² ²
²²     ²²
² ²²   ²² ²
²  ²²  °°° °°°  ²²  ²
  ²²² ² ² °±± ²² ±±° ² ² ²²²  
²²²   ² ±²² ²²± ²   ²²²
²²   ²²²² + J O I N + ²²²   ²²
²² ²  ²²²² ²  ² ²²
²   ²
²  When joining Linezer0 you are not just joining a group, but  ²
²  a family. We're a group built on friendship, devotion, respect  ²
²  and of course the continous learning. If you are one of those  ²
²  whom are just here for the glory and releases, then you have  ²
²  found the wrong group. Hard work and dedication is what has  ²
²  brought us to where we are today, and it is that we will  ²
²  demand from you as well.  ²
²   ²
²  CRACKERS  ²
²  To be able to be accepted as a cracker in Linezer0, you will  ²
²  need to have at least 6 months of experience from other groups  ²
²  and have at least 2 people that can vouche for you before we  ²
²  will even concider talking with you.  ²
²   ²
²  Open positions  ²
²  * Keygenner s - able to analyse and keygen advanced  ²
²  protection schemes. You will be working with the other  ²
²  keygenners to be able to meet the advanced protections  ²
²  with a joint effort.  ²
²  * Dongle cracker s - need to have experience in one or  ²
²  more of the following dongles, FlexLM, SentinelLM, HASP,  ²
²  CRYPKEY and/or custom made license managers. We always  ²
²  got big projects that you can undertake, and with the  ²
²  dongle crew you will be working in a joint effort to  ²
²  find sollutions - preferrably complete emulators for  ²
²  the different solutions.  ²
²   ²
²  CODERS  ²
²  You have knowledge regarding protections like ASPACK and  ²
²  ARMADILLO, and are able to code tools that can either analyse  ²
²  those, or even able to unpack them. Further we require that  ²
²  you have at least 4 years of coding experience, and can show us  ²
²  earlier achievements either through system analysis and/or  ²
²  programs you have developed.  ²
²   ²
²  Open positions  ²
²  * Cracktro programmer - we are looking for an experienced  ²
²  programmer that can develop a complete cracktro and a  ²
²  update system for that particular cracktro. Experience  ²
²  from the demo scene is preferred, but achievements that  ²
²  can show your skills can also be accepted.  ²
²  * General programmer s - you will be recieving projects  ²
²  that will range from everything from updating our  ²
²  existing tools, as well as develop new tools that will  ²
²  be useful for the group.  ²
²   ²
²  SUPPLIERS  ²
²  You work as a engineer or something similar where you got  ²
²  access to the latest software in the CAD/CAM area. Preferrably  ²
²  with experience in the supplied software as testing your own  ²
²  supply would also be required to ensure validity. We are also  ²
²  interrested in people able to supply us software in the  ²
²  GRAPHICS/MUSIC/PROGRAMMING area. One time suppliers are not  ²
²  welcome, a steady base of supplies will be required.  ²
²   ²
²  SITES  ²
²  If you run a dedicated site, on a 100mbit link, a well  ²
²  supported site that have at least 6 months of up-time and  ²
²  decent affiliation. Then your site might be of interrest to  ²
²  us. Do note that we do NOT accept site offers from the US, DE  ²
²  and AT.  ²
²   ²
² ²   ² ²
²²     ²²
² ²²   ²² ²
²  ²²  °°° °°°  ²²  ²
  ²²² ² ² °±± ²² ±±° ² ² ²²²  
²²²   ² ±²² ²²± ²   ²²²
²²   ²²²² + L E G A L + ²²²   ²²
²² ²  ²²²² ²  ² ²²
²   ²
²  First of all you should know that we do NOT release our cracks  ²
²  so that you the end-user can benefit from it in the term of  ²
²  using software or any other of our releases without buying  ²
²  the required licenses. Linezer0 however believe that everyone  ²
²  should have the option to backup their program/game and be  ²
²  able to run it without any problems.  ²
²   ²
²  Further we do NOT in any way condone the spreading of our  ²
²  cracks, in other words we do NOT spread the releases to any  ²
²  websites, P2P networks or any other public available location  ²
²  and we urge that our releases should not be spread like that  ²
²  at all.  ²
²   ²
²  We -Linezer0- has nothing to do with the distribution of these  ²
²  cracks, it is all done by third parties. As such, and  ²
²  according to the laws where the individuals of Linezer0 reside,  ²
²  it is not our responsibility what others desides to do with  ²
²  these releases. However, let it be said quite clearly;  ²
²   ²
²  We DO NOT in any way condone the selling or redistribution  ²
²  of our cracks, this was NEVER our intention.  ²
²   ²
²  Linezer0 does NOT take any responsibility of computer-loss  ²
²  or any data-errors that may occur from using our cracks.  ²
²  Keep in mind that you are using a third party sollution to  ²
²  something we did not develop in the first place.  ²
²   ²
²  Do note that the usage of our cracks are legal in most  ²
²  countries outside the United States, IF and ONLY IF you own a  ²
²  full copy of the program/game - then you may use our cracks  ²
²  for backup purposes, and only that. It remains to be seen how  ²
²  affected you are of the End User License Agreements EULAs .  ²
²  They can't supersede domestic laws, remember that.  ²
²   ²
²  According to the DMCA ACT in the Unites States, you have no  ²
²  rights to circumvent a copy protection. Beware, they will  ²
²  punish you harder than if you stole the shrinkwrapped software  ²
²  in a mall. Though Linezer0's base of operation does not reside  ²
²  in the Unites States, and thus we are NOT bound to the  ²
²  US legislations like  ²
²   ²
²  * No Electronic Theft Act  ²
²  * Digital Millenium Copyright Act  ²
²  * The Patriot Act  ²
²  * other US legislations  ²
²   ²
²  You should ALWAYS buy the software that you do use, or find  ²
²  suitable Open Source replacements as there are loads , we do!  ²
²   ²
²  By using our cracks you automatically agree  ²
²  to the written agreement above, and thus the responsibility  ²
²  regarding whetever you are affected by any EULAs is  ²
²  with YOU and YOU only.  ²
² ²   ² ²
²²     ²²
² ²²   ²² ²
²  ²²  °°° °°°  ²²  ²
  ²²² ² ² °±± ²² ±±° ² ² ²²²  
²²²   ² ±²² ²²± ²   ²²²
²²   ²²²² + G R E E T S + ²²²   ²²
²² ²  ²²²² ²  ² ²²
²   ²
²  HERiTAGE, RAZOR1911, F4CG, EMPHASiS, ZENiTH, MYTH  ²
²  GHOST RiDERS, LEGENDS NEVER DiE, ENFUSiA, BiN  ²
²  FATiGUED COURiERS NETWORK FCN  ²
² ²  CHEMiCAL REACTiON CRO  ² ²
²²     ²²
² ²²   ²² ²
²  ²²  °°° °°°  ²²  ²
  ²²² ² ² °±± ²² ±±° ² ² ²²²  
²²²   ² ±²² ²²± ²   ²²²
²²   ²²²²+ C O N T A C T +²²²   ²²
²² ²  ²²²² ²  ² ²²
²   ²
²   ²
²  If you want to contact Linezer0 for any reason, then feel  ²
²  free to do so using the email supplied below - requests for  ²
²  cracks, files or anything related to our releases is  ²
²  automatically ignored using scripts , so by all means, feel  ²
²  free to continue to send them, we won't even recieve them.  ²
²   ²
²  ² EMAIL linezer0@nerdshack.com ²  ²
² ²  UPDATED 7th of January 2006   ²
²²     ²²
²     ²
²  ²  ²  ²
  ²    ²  
² ²²²  °°°      °°°  ²²² ²
² ² ² °±± ²²  ²² ±±° ² ² ²
  ² ±²²   ²²± ²  
 ²²²²²²   ²²²²²² 
²²² ascii proudly done ²²²²
²² by cpN of cRo ²²
²²  in 2oo6  ²²
 ²   ² 
²² ²     ² ²²
²²² ² ²²²
²  ²
²²
²

[安全检测]
★未经过安全检测
[安装测试]
★未经过安装测试,使用者后果自负与本论坛无关。
[免责声明]
★本帖介绍的文本内容转自网络,如有出入则以官方站点公布之信息为准,凡摘自网络相关图文介绍内容的本帖不另行标注出处,原创作者如有异议可提出以便删除。
★关于软件破解及注册机可能被杀毒软件报病毒或间谍木马(若已检测到的则将在帖中特别标注),请自行甄别和取舍,不另行加以解释。
★资源下载后请对文件做必要的安全检测,该下载内容仅限于个人测试学习之用,不得用于商业用途,并且请在下载后24小时内删除。
★各计算机系统环境各不相同,因此不保证该软件完全兼容于你的计算机系统,最终解决软件安装运行问题请联络官方站点寻求相关技术支持。
★凡标注为下载链接转自其他站点的,无法保证资源的供源以及资源本身等情况的完整性和可用性(不可控)。
★资源版权归作者及其公司所有,如果你喜欢,请购买正版。