public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "czx211355007 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/107836] x86_64 inline functions -O2/-O3 optimization error
Date: Thu, 24 Nov 2022 08:36:40 +0000	[thread overview]
Message-ID: <bug-107836-4-bqZszAFRmg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107836-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Zixuan Chen <czx211355007 at gmail dot com> ---
I think there is a data dependency between the second asm statement and the
third, a read-after-write one. If the third one is moved to the top then we
can't get the correct value of mm5(mm0). Also, could you explain why the
result using -O1 to compile is correct as expected where the asm statements
remain in the same order as they should be?

schwab@linux-m68k.org <gcc-bugzilla@gcc.gnu.org> 于2022年11月23日周三 23:48写道:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107836
>
> Andreas Schwab <schwab@linux-m68k.org> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>          Resolution|---                         |INVALID
>              Status|UNCONFIRMED                 |RESOLVED
>
> --- Comment #2 from Andreas Schwab <schwab@linux-m68k.org> ---
> There is no dependency whatsoever between the asm statements, thus they
> can be
> moved around freely. Especially the third one is producing a constant
> output as
> seen by the compiler, thus moving it to the top of the function is
> perfectly
> valid.
>
> --
> You are receiving this mail because:
> You reported the bug.

      parent reply	other threads:[~2022-11-24  8:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-23 15:04 [Bug c/107836] New: " czx211355007 at gmail dot com
2022-11-23 15:11 ` [Bug c/107836] " pinskia at gcc dot gnu.org
2022-11-23 15:48 ` schwab@linux-m68k.org
2022-11-24  8:36 ` czx211355007 at gmail dot com [this message]

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-107836-4-bqZszAFRmg@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).