public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gdr at integrable-solutions dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/24902] COMPLEX_ASSIGN is wrong
Date: Wed, 16 Nov 2005 20:24:00 -0000	[thread overview]
Message-ID: <20051116202423.19655.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24902-6528@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from gdr at integrable-solutions dot net  2005-11-16 20:24 -------
Subject: Re:  COMPLEX_ASSIGN is wrong

"pinskia at physics dot uc dot edu" <gcc-bugzilla@gcc.gnu.org> writes:

| Subject: Re:  COMPLEX_ASSIGN is wrong
| 
| > yields an lvalue.  do whatever you want in the *middle end*, but be
| > sure you don't transmute that basic semantics constraint.
| 
| Gaby, it also prevents a huge amount of optimizations so what is
| the difference from saying it is wrong?

You're putting optimization before semantics; -that- is wrong.  I'm
not interested in the fastest program if it does not meet my needs.
If __imag__ z yields a modifiable lvalue, then it follows, by ordinary
language rules that it can be used on the left hand side of built-in
"=".  In C, the resulting expresion is an rvalue; in C++ it is an
lvalue.  No amount of bizarre extension should break those simple
rules.  

| The issue comes down to what does
| __imag__ a = b; really means.

No, it comes down to what "__imag__ a" means.

-- Gaby


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24902


  parent reply	other threads:[~2005-11-16 20:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-16 18:57 [Bug libfortran/24902] New: " pinskia at gcc dot gnu dot org
2005-11-16 18:58 ` [Bug libfortran/24902] " pinskia at gcc dot gnu dot org
2005-11-16 19:43 ` gdr at integrable-solutions dot net
2005-11-16 19:50 ` pinskia at physics dot uc dot edu
2005-11-16 19:53 ` pinskia at gcc dot gnu dot org
2005-11-16 20:24 ` gdr at integrable-solutions dot net [this message]
2005-11-16 20:27 ` gdr at integrable-solutions dot net
2005-11-16 20:29 ` pinskia at physics dot uc dot edu
2005-11-16 20:39 ` gdr at integrable-solutions dot net
2005-11-16 22:45 ` kargl at gcc dot gnu dot org
2007-01-05 14:06 ` fxcoudert at gcc dot gnu dot org

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=20051116202423.19655.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).