public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pthaugen at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/102783] [powerpc] FPSCR manipulations cannot be relied upon Date: Fri, 15 Oct 2021 19:27:19 +0000 [thread overview] Message-ID: <bug-102783-4-bVvC5tg9Es@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102783-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102783 pthaugen at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pthaugen at gcc dot gnu.org --- Comment #2 from pthaugen at gcc dot gnu.org --- I’ll note that an inline asm stmt appears to be a barrier for the scheduler, but apparently not for other parts of the compiler. For example on the following code: double d; void foo(double *dp, double c) { double e; e = c + d; asm volatile (""); *dp = e + d; return; } The scheduling dumps show that the asm volatile has dependencies on all insns before and after it. But that doesn’t really help because the first addition stmt gets moved past the asm volatile at expand time.
next prev parent reply other threads:[~2021-10-15 19:27 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-15 16:15 [Bug target/102783] New: " pc at us dot ibm.com 2021-10-15 16:37 ` [Bug target/102783] " pinskia at gcc dot gnu.org 2021-10-15 19:27 ` pthaugen at gcc dot gnu.org [this message] 2021-10-15 19:31 ` segher at gcc dot gnu.org 2021-10-15 19:53 ` pinskia at gcc dot gnu.org 2021-10-18 6:27 ` rguenth at gcc dot gnu.org 2021-10-18 21:52 ` joseph at codesourcery dot com 2021-10-19 10:28 ` segher at gcc dot gnu.org 2021-10-19 10:41 ` segher at gcc dot gnu.org 2021-10-19 15:30 ` joseph at codesourcery dot com 2021-10-28 14:07 ` rguenth at gcc dot gnu.org 2022-08-26 12:11 ` glisse at gcc dot gnu.org 2023-01-07 21:14 ` glisse at gcc dot gnu.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=bug-102783-4-bVvC5tg9Es@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: linkBe 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).