From: Mark Mitchell <mark@codesourcery.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Gerald Pfeifer <gerald@pfeifer.com>,
Eric Botcazou <ebotcazou@libertysurf.fr>,
gcc@gcc.gnu.org
Subject: Re: GCC Release Status (2003-10-03)
Date: Sun, 05 Oct 2003 19:52:00 -0000 [thread overview]
Message-ID: <1065383550.32110.361.camel@doubledemon.codesourcery.com> (raw)
In-Reply-To: <20031004064117.GG12344@sunsite.ms.mff.cuni.cz>
On Fri, 2003-10-03 at 23:41, Jakub Jelinek wrote:
> On Sat, Oct 04, 2003 at 09:32:55AM +0200, Gerald Pfeifer wrote:
> > On Sat, 4 Oct 2003, Eric Botcazou wrote:
> > > Even regressions wrt to the previous release? See PR 12223.
> >
> > If PR 12223 really breaks QT and OpenOffice, it looks like a real
> > show-stopper. :-(
>
> PR 12223 is most likely fixed, it just needs someone to verify on OOo
> (certainly QT/KDE works for us again here).
The test case in the PR is fixed, according to your notes. Therefore,
I've closed the PR.
Now, there is the broader question of "do QT and OpenOffice work?"
(This PR addressed a specific code-generation problem, which is now
fixed.)
From what you say, QM and OpenOffice are OK. Therefore, I don't see a
showstopper here. If someone finds a problem with those applications, a
new PR should be filed.
Thanks,
--
Mark Mitchell <mark@codesourcery.com>
CodeSourcery, LLC
next prev parent reply other threads:[~2003-10-05 19:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-03 22:51 Mark Mitchell
2003-10-03 22:59 ` Gerald Pfeifer
2003-10-04 0:23 ` ping, RFA (try 2). DEBUG mainainters: Where to put location_t info? Carlo Wood
2003-10-04 6:19 ` GCC Release Status (2003-10-03) Eric Botcazou
2003-10-04 7:32 ` Gerald Pfeifer
2003-10-04 8:44 ` Jakub Jelinek
2003-10-05 19:52 ` Mark Mitchell [this message]
2003-10-05 19:55 ` Mark Mitchell
2003-10-04 2:25 Michael Elizabeth Chastain
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=1065383550.32110.361.camel@doubledemon.codesourcery.com \
--to=mark@codesourcery.com \
--cc=ebotcazou@libertysurf.fr \
--cc=gcc@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=jakub@redhat.com \
/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).