public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bisqwit at iki dot fi" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/31485] C complex numbers, amd64 SSE, missed optimization opportunity
Date: Tue, 21 Apr 2020 09:06:49 +0000	[thread overview]
Message-ID: <bug-31485-4-d8WDORl4ob@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-31485-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=31485

--- Comment #25 from Joel Yliluoma <bisqwit at iki dot fi> ---
(In reply to Jakub Jelinek from comment #24)
> on x86 read e.g. about MXCSR register and in the description of each
> instruction on which Exceptions it can raise.

So the quick answer to #15 is that addps instruction may raise exceptions. Ok,
thanks for clearing that up. My bad. So it seems that LLVM relies on the
assumption that the upper portions of the register are zeroed, and this is what
you said in the first place.

  parent reply	other threads:[~2020-04-21  9:06 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-31485-4@http.gcc.gnu.org/bugzilla/>
2020-04-21  6:43 ` bisqwit at iki dot fi
2020-04-21  7:07 ` rguenth at gcc dot gnu.org
2020-04-21  7:17 ` bisqwit at iki dot fi
2020-04-21  7:37 ` rguenth at gcc dot gnu.org
2020-04-21  8:18 ` bisqwit at iki dot fi
2020-04-21  8:23 ` jakub at gcc dot gnu.org
2020-04-21  8:29 ` rguenther at suse dot de
2020-04-21  8:32 ` jakub at gcc dot gnu.org
2020-04-21  8:33 ` jakub at gcc dot gnu.org
2020-04-21  8:34 ` bisqwit at iki dot fi
2020-04-21  8:43 ` jakub at gcc dot gnu.org
2020-04-21  8:47 ` rguenther at suse dot de
2020-04-21  8:51 ` bisqwit at iki dot fi
2020-04-21  8:58 ` jakub at gcc dot gnu.org
2020-04-21  9:06 ` bisqwit at iki dot fi [this message]
2021-08-16 21:29 ` pinskia at gcc dot gnu.org
2021-08-16 21:29 ` [Bug tree-optimization/31485] " pinskia at gcc dot gnu.org
2022-02-07  8:48 ` rguenth at gcc dot gnu.org
2023-10-01 18:45 ` pinskia at gcc dot gnu.org
2007-04-05 11:29 [Bug rtl-optimization/31485] New: " bisqwit at iki dot fi
2007-04-09 17:48 ` [Bug rtl-optimization/31485] " rguenth at gcc dot gnu dot org
2008-07-29 22:07 ` victork at gcc dot gnu dot org
2008-08-02 12:23 ` rguenth at gcc dot gnu dot org
2008-08-02 13:01 ` ubizjak at gmail dot com
2008-08-02 13:19 ` rguenth at gcc dot gnu dot org
2010-04-17  0:28 ` ddesics at gmail dot com
2010-04-17 11:11 ` rguenth at gcc dot gnu dot org
2010-04-21 11:33 ` irar at il dot ibm dot com
2010-04-21 11:44 ` rguenther at suse dot de
2010-04-21 18:34 ` irar at il dot ibm dot com

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=bug-31485-4-d8WDORl4ob@http.gcc.gnu.org/bugzilla/ \
    --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).