public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/103350] [12 Regression] wrong code with -Os -fno-tree-ter on aarch64-unknown-linux-gnu since r12-2288-g8695bf78dad1a42636775843ca832a2f4dba4da3
Date: Mon, 22 Nov 2021 10:42:11 +0000 [thread overview]
Message-ID: <bug-103350-4-fEQ2kPQV3B@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103350-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103350
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |12.0
Summary|wrong code with -Os |[12 Regression] wrong code
|-fno-tree-ter on |with -Os -fno-tree-ter on
|aarch64-unknown-linux-gnu |aarch64-unknown-linux-gnu
| |since
| |r12-2288-g8695bf78dad1a4263
| |6775843ca832a2f4dba4da3
Priority|P3 |P1
--- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
Started with r12-2288-g8695bf78dad1a42636775843ca832a2f4dba4da3.
next prev parent reply other threads:[~2021-11-22 10:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-21 19:44 [Bug rtl-optimization/103350] New: wrong code with -Os -fno-tree-ter on aarch64-unknown-linux-gnu zsojka at seznam dot cz
2021-11-21 22:22 ` [Bug rtl-optimization/103350] " pinskia at gcc dot gnu.org
2021-11-22 9:23 ` marxin at gcc dot gnu.org
2021-11-22 10:42 ` marxin at gcc dot gnu.org [this message]
2021-11-22 10:43 ` [Bug rtl-optimization/103350] [12 Regression] wrong code with -Os -fno-tree-ter on aarch64-unknown-linux-gnu since r12-2288-g8695bf78dad1a42636775843ca832a2f4dba4da3 marxin at gcc dot gnu.org
2021-12-13 8:36 ` tnfchris at gcc dot gnu.org
2021-12-13 9:02 ` tnfchris at gcc dot gnu.org
2021-12-15 10:26 ` cvs-commit at gcc dot gnu.org
2021-12-15 10:29 ` tnfchris 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-103350-4-fEQ2kPQV3B@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).