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 14:08:21 +0000 [thread overview] Message-ID: <bug-96854-4-K7L4mlTpPN@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 #14 from Jakub Jelinek <jakub at gcc dot gnu.org> --- The versioning is well documented https://gcc.gnu.org/develop.html#num_scheme and the only way how things are fixed is fixing on the mainline and when needed on still open release branches. Those will become an upcoming release at some later point. Generally, it is advisable to use snapshots from the release branches, as otherwise one misses dozens to hundreds of bugfixes that were fixed since the last release.
next prev parent reply other threads:[~2020-09-06 14:08 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 [this message] 2020-09-06 15:17 ` already5chosen at yahoo dot com 2020-09-06 15:22 ` jakub at gcc dot gnu.org 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-K7L4mlTpPN@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: linkBe 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).