public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rob1weld at aol dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/40028] New: RFE - Add GPU acceleration library to gcc Date: Tue, 05 May 2009 16:19:00 -0000 [thread overview] Message-ID: <bug-40028-13830@http.gcc.gnu.org/bugzilla/> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 2484 bytes --] RFE - It would be great if gcc had a couple (ATI / NVidia) of GPU libraries that gcc could use to speed up programs similar to what is done here: http://www.pgroup.com/resources/accel.htm " The PGI 8.0 x64+GPU compilers automatically analyze whole program structure and data, split portions of the application between the x64 CPU and GPU as specified by user directives, and define and generate an optimized mapping of loops to automatically use the parallel cores, hardware threading capabilities and SIMD vector capabilities of modern GPUs. In addition to directives and pragmas that specify regions of code or functions to be accelerated, the PGI Fortran and C compilers will support user directives that give the programmer fine-grained control over the mapping of loops, allocation of memory, and optimization for the GPU memory hierarchy. The PGI compilers generate unified x64+GPU object files and executables that manage all movement of data to and from the GPU device while leveraging all existing host-side utilitieslinker, librarians, makefilesand require no changes to the existing standard HPC Linux/x64 programming environment. " A demo of a program written in the OpenCL Language is here: http://www.youtube.com/watch?v=r1sN1ELJfNo&feature=channel_page The "GPGPU Programming Developer" Webpage is here: http://gpgpu.org/developer Some applications can be ran hundreds of times faster, see this page at NVidia. http://www.nvidia.com/object/cuda_home.html If we could use run-time-linking to select either the ATI or NVidia (PlayStation?) library at run-time then gcc would remain portable and offer the speedup on any platform that utilized a graphics card with a GPU (not just x86). The middle end could attempt to determine which functions (or groups of code, inlinable, functions, loops, etc.) would be best to offload to the GPU (if a supported one were detected) and then resulting program would run much faster for most people by using the GPU as a coprocessor. Thanks, Rob -- Summary: RFE - Add GPU acceleration library to gcc Product: gcc Version: 4.5.0 Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: middle-end AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: rob1weld at aol dot com GCC build triplet: * GCC host triplet: * GCC target triplet: * http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40028
next reply other threads:[~2009-05-05 16:19 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-05-05 16:19 rob1weld at aol dot com [this message] 2009-05-05 16:25 ` [Bug middle-end/40028] " pinskia at gcc dot gnu dot org 2009-05-18 17:36 ` rob1weld at aol dot com 2009-05-20 13:10 ` rob1weld at aol dot com 2009-10-07 11:22 ` rob1weld at aol dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-40028-13830@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).