public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/109326] Bad assembler code generation for valid C on 886-64
Date: Wed, 29 Mar 2023 02:35:55 +0000	[thread overview]
Message-ID: <bug-109326-4-UD1zT5p9N1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109326-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Steve Thompson from comment #3)
> However I don't understand why olock_reset_op() is so large.  It's
> a trivial initializer for a descriptor with an array of olock_op_element
> structures appended.  There's no way it should look like what I quoted.  I'd
> be happy if I am experiencing a fever-dream over nothing due to ignorance,
> but I am not convinced that that is the case.  If I am wrong I will be very
> disappointed.

GCC unrolled the loop via vectorizing it.

  parent reply	other threads:[~2023-03-29  2:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-29  1:04 [Bug c/109326] New: " susurrus.of.qualia at gmail dot com
2023-03-29  1:23 ` [Bug middle-end/109326] " pinskia at gcc dot gnu.org
2023-03-29  1:38 ` pinskia at gcc dot gnu.org
2023-03-29  2:26 ` susurrus.of.qualia at gmail dot com
2023-03-29  2:35 ` pinskia at gcc dot gnu.org [this message]
2023-03-30  2:18 ` [Bug middle-end/109326] Sub-optimal assembler code generation for valid C on x86-64 susurrus.of.qualia at gmail dot com
2023-03-30  2:32 ` susurrus.of.qualia at gmail 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-109326-4-UD1zT5p9N1@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).