From: Mark Mitchell <mark@codesourcery.com>
To: Andreas Jaeger <aj@suse.de>, "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: PR 7306 (C++/i86 thunk bug with varargs)
Date: Tue, 22 Oct 2002 11:11:00 -0000 [thread overview]
Message-ID: <30450000.1035304882@warlock.codesourcery.com> (raw)
In-Reply-To: <hosmyyd038.fsf@gee.suse.de>
--On Tuesday, October 22, 2002 04:23:07 PM +0200 Andreas Jaeger
<aj@suse.de> wrote:
>
> PR 7306 is a regression from gcc 2.95. In July Nathan made a patch
> for it:
> http://gcc.gnu.org/ml/gcc-patches/2002-07/msg00650.html
>
> But this patch seems to not made it in, it seems that Nathan was
> waiting for some patch from Zack to fix multiple entry points.
>
> What's the status of these patches and the PR?
It's very embarassing, really. I didn't know about/forgot about
Nathan's patch and independently reinvented it last week. In any
case, it is now checked in and the PR is closed.
The multiple entry point stuff is still in the queue, but for now it
still makes sense to use Nathan's approach.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
next prev parent reply other threads:[~2002-10-22 16:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-22 10:00 Andreas Jaeger
2002-10-22 11:11 ` Mark Mitchell [this message]
2002-10-22 12:08 ` Andreas Jaeger
2002-10-22 13:35 ` Mark Mitchell
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=30450000.1035304882@warlock.codesourcery.com \
--to=mark@codesourcery.com \
--cc=aj@suse.de \
--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).