From: Jim Wilson <wilson@cygnus.com>
To: Richard Henderson <rth@cygnus.com>
Cc: Joern Rennecke <amylaar@cygnus.co.uk>, egcs@cygnus.com
Subject: Re: alpha regression on 920625-1
Date: Tue, 28 Apr 1998 19:14:00 -0000 [thread overview]
Message-ID: <199804290214.TAA24884@rtl.cygnus.com> (raw)
In-Reply-To: <19980427135933.01385@dot.cygnus.com>
No, the problem is after this. The read from varargs is fine. The
problem comes when the struct must be spilled from the registers it
was read into.
This is the same problem that is causing Ulrich's glibc builds to fail,
except that it is happening with a union in this case.
Your patch doesn't entirely fix the problem, since structs/unions of 1 word
will still fail.
I think we need to consider reverting some of the recent alias changes,
as they are causing too much trouble.
Jim
next prev parent reply other threads:[~1998-04-28 19:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-27 0:33 Richard Henderson
1998-04-27 11:10 ` Joern Rennecke
1998-04-27 13:59 ` Richard Henderson
1998-04-28 19:14 ` Jim Wilson [this message]
1998-04-28 21:59 ` Richard Henderson
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=199804290214.TAA24884@rtl.cygnus.com \
--to=wilson@cygnus.com \
--cc=amylaar@cygnus.co.uk \
--cc=egcs@cygnus.com \
--cc=rth@cygnus.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).