This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: GCC Status Report (2004-03-09)
- From: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
- To: jakub at redhat dot com
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Thu, 1 Apr 04 08:35:59 EST
- Subject: Re: GCC Status Report (2004-03-09)
The object can be huge, allocating a temporary of the same size can be
prohibitive, at least in certain environments (e.g. when stack size
is very limited).
Indeed it *can* be, but remember that this is only when the result is /u
and all fields aren't initialized. No method is perfect here, but I
feel this is the best approach.
I think initializing directly into the object without /u, optimization
barrier and using /u from that point onwards should generate better code.
I'm not so sure and I don't like the idea of the "optimization barrier".
I think it's a kludge that may not work as well as we like. It'll also
generate worse code in the case of smaller objects, which I think are the
more common.