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 c/107127] [11/12/13 Regression] Long compile times on code with C complex since r11-3299-gcba079f354a55363
Date: Mon, 03 Oct 2022 09:31:43 +0000 [thread overview]
Message-ID: <bug-107127-4-QnvgP1e8Re@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107127-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107127
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
Summary|[Regression 11/12] Long |[11/12/13 Regression] Long
|compile times on code with |compile times on code with
|C complex |C complex since
| |r11-3299-gcba079f354a55363
CC| |marxin at gcc dot gnu.org,
| |sandra at codesourcery dot com
Last reconfirmed| |2022-10-03
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Started with r11-3299-gcba079f354a55363.
Thanks for the bug report.
next prev parent reply other threads:[~2022-10-03 9:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 2:03 [Bug c/107127] New: [Regression 11/12] Long compile times on code with C complex inform at tiker dot net
2022-10-03 9:31 ` marxin at gcc dot gnu.org [this message]
2022-10-03 9:53 ` [Bug c/107127] [11/12/13 Regression] Long compile times on code with C complex since r11-3299-gcba079f354a55363 marxin at gcc dot gnu.org
2022-10-03 19:49 ` pinskia at gcc dot gnu.org
2022-10-03 19:52 ` pinskia at gcc dot gnu.org
2022-10-06 9:59 ` rguenth at gcc dot gnu.org
2022-11-22 11:10 ` jakub at gcc dot gnu.org
2022-11-23 18:10 ` cvs-commit at gcc dot gnu.org
2022-11-23 18:11 ` [Bug c/107127] [11/12 " jakub at gcc dot gnu.org
2022-11-24 9:34 ` cvs-commit at gcc dot gnu.org
2023-02-10 17:43 ` cvs-commit at gcc dot gnu.org
2023-02-10 17:44 ` cvs-commit at gcc dot gnu.org
2023-02-10 17:57 ` [Bug c/107127] [11 " jakub at gcc dot gnu.org
2023-05-02 20:12 ` cvs-commit at gcc dot gnu.org
2023-05-02 20:12 ` cvs-commit at gcc dot gnu.org
2023-05-03 9:29 ` 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-107127-4-QnvgP1e8Re@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).