public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/109213] [13 Regression] -Os generates significantly more code since r13-723
Date: Tue, 21 Mar 2023 08:45:36 +0000 [thread overview]
Message-ID: <bug-109213-4-CQaU1md1AV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109213-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109213
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2023-03-21
CC| |jakub at gcc dot gnu.org
Ever confirmed|0 |1
Keywords|needs-bisection |
Summary|[13 Regression] -Os |[13 Regression] -Os
|generates significantly |generates significantly
|more code |more code since r13-723
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
This changed with r13-723-g1adf11822bd48f4d65156b7642514630c08c4d00
next prev parent reply other threads:[~2023-03-21 8:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 11:53 [Bug tree-optimization/109213] New: [13 Regression] -Os generates significantly more code theodort at inf dot ethz.ch
2023-03-20 13:07 ` [Bug tree-optimization/109213] " rguenth at gcc dot gnu.org
2023-03-20 17:36 ` pinskia at gcc dot gnu.org
2023-03-20 17:36 ` pinskia at gcc dot gnu.org
2023-03-20 17:39 ` pinskia at gcc dot gnu.org
2023-03-20 17:54 ` pinskia at gcc dot gnu.org
2023-03-21 8:45 ` jakub at gcc dot gnu.org [this message]
2023-03-21 13:37 ` [Bug tree-optimization/109213] [13 Regression] -Os generates significantly more code since r13-723 rguenth at gcc dot gnu.org
2023-03-27 7:43 ` rguenth at gcc dot gnu.org
2023-03-29 15:04 ` hubicka at gcc dot gnu.org
2023-04-26 6:58 ` [Bug tree-optimization/109213] [13/14 " rguenth at gcc dot gnu.org
2023-07-27 9:25 ` rguenth at gcc dot gnu.org
2024-05-21 9:14 ` [Bug tree-optimization/109213] [13/14/15 " jakub 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-109213-4-CQaU1md1AV@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).