should backport OpenMP 3.0 to gcc-4.3.1 for Intrepid
Bug #253185 reported by
Qichang Liang
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gcc-4.3 (Ubuntu) |
Won't Fix
|
Wishlist
|
Unassigned |
Bug Description
Binary package hint: gcc-4.3
gcc implementation of the new openmp-3.0 standard has been merged into the svn trunk in June
openmp-3.0 contains quite a number of new features and redhat has already backported openmp-3.0 to 4.3.1. To make openmp-3.0 into Intrepid, which would help many multi-core machines, should we also backport openmpi-3.0 to gcc-4.3.1 in Intrepid? Can we just lift Redhat's diff into our one?
http://
To post a comment you must log in.
Leung, Kai-Cheung schrieb: gcc.gnu. org/
> Public bug reported:
>
> Binary package hint: gcc-4.3
>
> gcc implementation of the new openmp-3.0 standard has been merged into
> the svn trunk in June
>
> http://
>
> openmp-3.0 contains quite a number of new features and redhat has
> already backported openmp-3.0 to 4.3.1. To make openmp-3.0 into
> Intrepid, which would help many multi-core machines, should we also
> backport openmpi-3.0 to gcc-4.3.1 in Intrepid? Can we just lift Redhat's
> diff into our one?
No, the diff contains more than the openmp backport.