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 target/106818] riscv produces bad low_sum while doing expansion of strict aligned stores/load
Date: Wed, 29 Nov 2023 18:45:05 +0000 [thread overview]
Message-ID: <bug-106818-4-2CpZqvYaUN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106818-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106818
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #13 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Dup of bug 100604.
*** This bug has been marked as a duplicate of bug 100604 ***
prev parent reply other threads:[~2023-11-29 18:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-02 19:26 [Bug c/106818] New: code is genereated differently with or without 'extern' pangbw at gmail dot com
2022-09-02 19:28 ` [Bug c/106818] " pangbw at gmail dot com
2022-09-02 19:37 ` pinskia at gcc dot gnu.org
2022-09-02 19:38 ` [Bug middle-end/106818] " pinskia at gcc dot gnu.org
2022-09-02 20:03 ` palmer at gcc dot gnu.org
2022-09-02 22:29 ` pangbw at gmail dot com
2022-09-02 22:33 ` pangbw at gmail dot com
2022-09-02 22:37 ` pinskia at gcc dot gnu.org
2022-09-02 23:59 ` palmer at gcc dot gnu.org
2022-09-05 10:15 ` rguenth at gcc dot gnu.org
2022-10-21 16:22 ` pinskia at gcc dot gnu.org
2022-10-21 16:31 ` [Bug target/106818] riscv produces bad low_sum while doing expansion of strict aligned stores/load pinskia at gcc dot gnu.org
2022-10-21 16:33 ` pinskia at gcc dot gnu.org
2023-11-29 18:45 ` pinskia at gcc dot gnu.org [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-106818-4-2CpZqvYaUN@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).