From: Mark Mitchell <mark@codesourcery.com>
To: Diego Novillo <dnovillo@redhat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: GCC 4.1/4.2 Status Report (2005-11-18)
Date: Fri, 18 Nov 2005 16:24:00 -0000 [thread overview]
Message-ID: <437E0044.90200@codesourcery.com> (raw)
In-Reply-To: <200511180625.20688.dnovillo@redhat.com>
Diego Novillo wrote:
> On Friday 18 November 2005 03:48, Mark Mitchell wrote:
>
>
>>I would like to better understand the status of GOMP; is it going to be
>>ready for 4.2 within a couple of months?
>>
> Most definitely. We have been essentially waiting for 4.1 to branch.
> There are 5 modules to merge: library, C, C++, Fortran, middle-end.
> The FEs can be merged in more or less independently from library and
> middle-end.
Great news. (The GOMP entry on the projects list was just a link to the
project page; it didn't have this data.)
It seems like it makes sense to do the library and middle-end first, and
then the various front-ends in serial? Do you agree?
I'd like to have a look at the C++ bits before they go in, but I'll not
be looking to make life difficult. :-)
--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
(916) 791-8304
next prev parent reply other threads:[~2005-11-18 16:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-18 8:48 Mark Mitchell
2005-11-18 11:26 ` Diego Novillo
2005-11-18 16:24 ` Mark Mitchell [this message]
2005-11-18 16:46 ` Diego Novillo
2005-11-18 17:47 ` Mark Mitchell
2005-11-18 18:15 ` Mike Stump
2005-11-18 21:07 ` RTEMS GCC Status Report Joel Sherrill <joel@OARcorp.com>
2005-11-18 21:55 ` Laurent GUERBY
2005-11-18 22:05 ` Joel Sherrill <joel@OARcorp.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=437E0044.90200@codesourcery.com \
--to=mark@codesourcery.com \
--cc=dnovillo@redhat.com \
--cc=gcc@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: link
Be 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).