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 target/96854] [10 Regression] avx vectorizer breaks complex arithmetic
Date: Sun, 06 Sep 2020 15:22:18 +0000	[thread overview]
Message-ID: <bug-96854-4-3D24BSDrFv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96854-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96854

--- Comment #16 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
If you want bugfixes as in this case.  The cadence on the release branches is
gradually slowing down, the last release is usually about a year about the one
before that.  It is already quite a lot of work to backport fixes to release
branches, maintaining some 10.1 and 10.2 etc. streams would be significantly
more, plus usually you want all bugfixes from the release branch, i.e. there
would be no difference between 10.2.fixes and 10.3.

  parent reply	other threads:[~2020-09-06 15:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-30 20:47 [Bug target/96854] New: " already5chosen at yahoo dot com
2020-08-31  6:50 ` [Bug target/96854] [10 Regression] " rguenth at gcc dot gnu.org
2020-08-31  9:36 ` jakub at gcc dot gnu.org
2020-08-31  9:52 ` rguenth at gcc dot gnu.org
2020-08-31  9:57 ` already5chosen at yahoo dot com
2020-08-31 11:20 ` rguenth at gcc dot gnu.org
2020-08-31 11:20 ` rguenth at gcc dot gnu.org
2020-08-31 11:35 ` rguenth at gcc dot gnu.org
2020-08-31 11:40 ` cvs-commit at gcc dot gnu.org
2020-08-31 11:43 ` cvs-commit at gcc dot gnu.org
2020-08-31 11:43 ` rguenth at gcc dot gnu.org
2020-09-06 10:56 ` already5chosen at yahoo dot com
2020-09-06 12:43 ` jakub at gcc dot gnu.org
2020-09-06 14:03 ` already5chosen at yahoo dot com
2020-09-06 14:08 ` jakub at gcc dot gnu.org
2020-09-06 15:17 ` already5chosen at yahoo dot com
2020-09-06 15:22 ` jakub at gcc dot gnu.org [this message]
2020-09-07  6:30 ` rguenther at suse dot de

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-96854-4-3D24BSDrFv@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).