From: "H. J. Lu" <hjl@lucon.org>
To: Greg Schafer <gschafer@zip.com.au>
Cc: kelledin@users.sourceforge.net, gcc@gcc.gnu.org, law@redhat.com,
gcc-patches@gcc.gnu.org, gcc-bugs@gcc.gnu.org
Subject: Re: optimization/7591: function-related struct copy bug
Date: Mon, 19 Aug 2002 07:09:00 -0000 [thread overview]
Message-ID: <20020819070910.A7359@lucon.org> (raw)
In-Reply-To: <20020819195002.A4321@tigers-lfs.nsw.bigpond.net.au>
On Mon, Aug 19, 2002 at 07:50:02PM +1000, Greg Schafer wrote:
> On Sun, Aug 18, 2002 at 08:36:04AM -0700, H. J. Lu wrote:
> > I am testing this now.
> >
> >
> > H.J.
>
> > 2002-08-18 H.J. Lu <hjl@gnu.org>
> >
> > * calls.c (store_one_arg): Remove ATTRIBUTE_UNUSED on
> > variable_size. Mark any slots used for the argument as in-use
> > only if we can't pass all arguments to a library call in
> > registers.
> >
> > --- gcc/calls.c.copy Sun Aug 18 07:35:11 2002
> > +++ gcc/calls.c Sun Aug 18 08:27:29 2002
>
> Fabulous. This fixed it for me. And I didn't see any regressions on
> i686-pc-linux-gnu (with the default arch in i386.c hacked to be i686)
>
Now, let's wait for someone to review it :-(.
H.J.
prev parent reply other threads:[~2002-08-19 7:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020818093401.A15946@tigers-lfs.nsw.bigpond.net.au>
[not found] ` <20020817184800.A2198@lucon.org>
[not found] ` <20020818152009.A29717@tigers-lfs.nsw.bigpond.net.au>
2002-08-18 0:09 ` Results for 3.2.1 20020816 (prerelease) testsuite on i686-pc-linux-gnu H. J. Lu
2002-08-18 8:06 ` optimization/7591: function-related struct copy bug H. J. Lu
2002-08-18 8:14 ` H. J. Lu
2002-08-18 8:36 ` H. J. Lu
2002-08-18 13:28 ` H. J. Lu
2002-08-19 2:50 ` Greg Schafer
2002-08-19 7:09 ` H. J. Lu [this message]
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=20020819070910.A7359@lucon.org \
--to=hjl@lucon.org \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=gschafer@zip.com.au \
--cc=kelledin@users.sourceforge.net \
--cc=law@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).