public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/96854] [10 Regression] avx vectorizer breaks complex arithmetic Date: Mon, 07 Sep 2020 06:30:58 +0000 [thread overview] Message-ID: <bug-96854-4-bK00lvH8c1@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 #17 from rguenther at suse dot de <rguenther at suse dot de> --- On Sun, 6 Sep 2020, already5chosen at yahoo dot com wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96854 > > --- Comment #15 from Michael_S <already5chosen at yahoo dot com> --- > Thank you. > That does not sound too different from what I assumed in post above. > 10.1.0 is release. Expected to be used by "normal" people. > 10.1.1 was for purpose of development of 10.2.0. Since release of 10.2.0 it is > obsolete. > 10.2.0 is release. Expected to be used by "normal" people. > 10.2.1 exists for purpose of development of 10.3.0. > > >> 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. > > That a little confusing. > I am compiler user, not compiler developer. Is it advisable for me to download > and compile snapshots ?! If you can wait then no, 10.x.0 are the "releases". If you are using pre-built binaries from some Linux distribution or other distributor then the distributor usually picks up the current branch head for you. > I would think that for people like me 3-4 month cadence of gcc releases is > already too quick. Well, all of GCC 10.x.[01] are one major release with a major release cadence of about one year. Everything else inbetween is just accumulated bugfixes with the "conveniece" of us doing 10.2.0 and later 10.3.0 at random points to officially release a tarball with accumulated bugfixes. You could say we should make it GCC 10.bugfix-nr and thus only have two numbers ;)
prev parent reply other threads:[~2020-09-07 6:30 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 2020-09-07 6:30 ` rguenther at suse dot de [this message]
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-bK00lvH8c1@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).