public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mitskevichmn at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/109493] Broken O2 optimization on s390x in GCC 13
Date: Thu, 13 Apr 2023 06:48:19 +0000 [thread overview]
Message-ID: <bug-109493-4-wNuxZBEf9d@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109493-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109493
--- Comment #4 from Mikhail Mitskevich <mitskevichmn at gmail dot com> ---
(In reply to Andrew Pinski from comment #1)
> belt_mac_st* st = &state;
> belt_mac_st* st2 = &state2;
> ((word*)(st->s))[0] = 0, ((word*)(st->s))[1] = 0;
> ((word*)(st->r))[0] = 0, ((word*)(st->r))[1] = 0;
> st->filled = 0;
>
> I am 99% sure those are aliasing rule violations.
>
> Does -fno-strict-aliasing help?
With -fno-strict-aliasing option code works as well as with -O1 option.
next prev parent reply other threads:[~2023-04-13 6:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 6:22 [Bug c/109493] New: " mitskevichmn at gmail dot com
2023-04-13 6:26 ` [Bug c/109493] " pinskia at gcc dot gnu.org
2023-04-13 6:28 ` [Bug middle-end/109493] " pinskia at gcc dot gnu.org
2023-04-13 6:35 ` sjames at gcc dot gnu.org
2023-04-13 6:48 ` mitskevichmn at gmail dot com [this message]
2023-04-13 6:55 ` mitskevichmn at gmail dot com
2023-04-13 7:25 ` mitskevichmn at gmail dot com
2023-04-13 8:37 ` xry111 at gcc dot gnu.org
2023-04-13 11:39 ` rguenth 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-109493-4-wNuxZBEf9d@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).