From: Nathan Sidwell <nathan@codesourcery.com>
To: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
Cc: Mark Mitchell <mark@codesourcery.com>,
gcc@gcc.gnu.org, stefan@space.twc.de
Subject: PR3909 and KDE2
Date: Tue, 09 Oct 2001 03:00:00 -0000 [thread overview]
Message-ID: <3BC2CA91.37B67022@codesourcery.com> (raw)
In-Reply-To: <200110082105.RAA88994@mail.acm.org>
Franz Sirl wrote:
> Oops, I forgot to mention that this is PR3909, testcase included in there.
> It's a pity this can't be solved in 3.0.2, it seemed to me that Nathan was
> nearly there already with 3.0.1.
Yes, well what looked like a little thread to tease out turned out to pull
a large amount of stuff with it. I've got a patch against 3.1 of a few
months ago, but it is (a) too large & complex for a dot release, (b)
untested against KDE. The good news is that (a) it did fix the remaining
3145 & 3909 failures, (b) it's related to /using/ the vbase offsets,
rather than creating them.
It kind of dropped off my radar. When I built KDE, I ran into some other
problems (4206) & I wasn't really sure what failures I was looking for. My
plan is to verify it works for KDE and then incrementally install it into 3.1
nathan
--
Dr Nathan Sidwell :: http://www.codesourcery.com :: CodeSourcery LLC
'But that's a lie.' - 'Yes it is. What's your point?'
nathan@codesourcery.com : http://www.cs.bris.ac.uk/~nathan/ : nathan@acm.org
next prev parent reply other threads:[~2001-10-09 3:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-08 12:19 PR3665 " Mark Mitchell
2001-10-08 14:03 ` Franz Sirl
[not found] ` <200110082105.RAA88994@mail.acm.org>
2001-10-09 3:00 ` Nathan Sidwell [this message]
2001-10-12 5:06 ` PR3909 " Franz Sirl
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=3BC2CA91.37B67022@codesourcery.com \
--to=nathan@codesourcery.com \
--cc=Franz.Sirl-kernel@lauterbach.com \
--cc=gcc@gcc.gnu.org \
--cc=mark@codesourcery.com \
--cc=stefan@space.twc.de \
/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).