From: David Edelsohn <dje@watson.ibm.com>
To: kenner@vlsi1.ultra.nyu.edu (Richard Kenner),
Fariborz Jahanian <fjahanian@apple.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Your assign_parms changes
Date: Thu, 18 Dec 2003 04:38:00 -0000 [thread overview]
Message-ID: <200312180312.hBI3CQT33458@makai.watson.ibm.com> (raw)
In-Reply-To: Message from kenner@vlsi1.ultra.nyu.edu (Richard Kenner) of "Wed, 17 Dec 2003 21:43:53 EST." <10312180243.AA08015@vlsi1.ultra.nyu.edu>
>>>>> Richard Kenner writes:
Richard> Right, I understand that, but then why the second change to prohibit this
Richard> from being done for CONCAT, which seems a very valuable case?
See the discussion thread started by Eric Botcazou:
http://gcc.gnu.org/ml/gcc-patches/2003-12/msg00031.html
The CONCAT generated for complex parameters produced additional spilling
and worse code.
David
next prev parent reply other threads:[~2003-12-18 3:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-18 4:28 Richard Kenner
2003-12-18 4:38 ` David Edelsohn [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-18 1:57 Richard Kenner
2003-12-18 4:01 ` David Edelsohn
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=200312180312.hBI3CQT33458@makai.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=fjahanian@apple.com \
--cc=gcc@gcc.gnu.org \
--cc=kenner@vlsi1.ultra.nyu.edu \
/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).