> Leung, Kai-Cheung schrieb:
> > 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://gcc.gnu.org/
> >
> > 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.
>
> --
> should backport OpenMP 3.0 to gcc-4.3.1 for Intrepid
> https://bugs.launchpad.net/bugs/253185
> You received this bug notification because you are a direct subscriber
> of the bug.
>
However how easy / difficult if we merge openmp-3.0 into ubuntu intrepid
gcc-4.3.1 without using redhat diff?
Quoting Matthias Klose <email address hidden>:
> Leung, Kai-Cheung schrieb: gcc.gnu. org/ /bugs.launchpad .net/bugs/ 253185
> > 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.
>
> --
> should backport OpenMP 3.0 to gcc-4.3.1 for Intrepid
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>
However how easy / difficult if we merge openmp-3.0 into ubuntu intrepid
gcc-4.3.1 without using redhat diff?