should backport OpenMP 3.0 to gcc-4.3.1 for Intrepid

Bug #253185 reported by Qichang Liang
2
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

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?

http://download.fedora.redhat.com/pub/fedora/linux/development/source/SRPMS//gcc-4.3.1-5.src.rpm

Revision history for this message
Matthias Klose (doko) wrote : Re: [Bug 253185] [NEW] should backport OpenMP 3.0 to gcc-4.3.1 for Intrepid

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.

Revision history for this message
Qichang Liang (kcleung-users) wrote :

Quoting Matthias Klose <email address hidden>:

> 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?

Revision history for this message
Matthias Klose (doko) wrote :

Leung, Kai-Cheung schrieb:
> However how easy / difficult if we merge openmp-3.0 into ubuntu intrepid
> gcc-4.3.1 without using redhat diff?

yoe, not me ;) I didn't look how difficult it is, but given our feature freeze
date approaching, you have to be quick. As an alternative, us the gcc-snapshot
package for experimental work.

  Matthias

Revision history for this message
Qichang Liang (kcleung-users) wrote :

Hi,

I am now trying to navigate the gcc sourcecode. Is the openmp-3.0 stuff
built into gfortran, gcc and g++, outside the libgomp subdirectory?

So when I try to merge openmp stuff into gcc-4.3.1 source file, which part
of the current gcc svn should I look at? I am a bit lost........
Obviously the the current trunk is 4.4 and I shouldn't merge everything at
the trunk to our gcc-4.3 source.....

Alternatively, I can use gcc-snapshot. By definition, it is a snapshot of
the trunk (future 4.4). Am I correct? If I use this snapshot and compile
my own programs, then if my programs links to other libraries (standard
libraries as well as some specific libraries), do I have to recompile ALL
these libraries using gcc-snapshot as well? This is my initial motivation
for thinking about backporting openmp 3.0 to gcc-4.3.1

Kai-Cheung

Quoting Matthias Klose <email address hidden>:

> Leung, Kai-Cheung schrieb:
> > However how easy / difficult if we merge openmp-3.0 into ubuntu
> intrepid
> > gcc-4.3.1 without using redhat diff?
>
> yoe, not me ;) I didn't look how difficult it is, but given our
> feature freeze
> date approaching, you have to be quick. As an alternative, us the
> gcc-snapshot
> package for experimental work.
>
> Matthias
>
> --
> 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.
>

Revision history for this message
Matthias Klose (doko) wrote :

you only have to use the snapshot for the parts using OpenMP 3.0. Make sure that you do use the shared libs from gcc-snapshot as well.

Changed in gcc-4.3:
importance: Undecided → Wishlist
Revision history for this message
Matthias Klose (doko) wrote :

tempted to close this one as won't fix.

Changed in gcc-4.3:
status: New → Triaged
Revision history for this message
Matthias Klose (doko) wrote :

closing as won't fix. please see the gcc-snapshot package (20081024-0ubuntu1) for openmp-3.0.

Changed in gcc-4.3:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.