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 rtl-optimization/59811] [4.8/4.9/5 Regression] Huge increase in memory usage and compile time in combine Date: Fri, 19 Dec 2014 13:29:00 -0000 [thread overview] Message-ID: <bug-59811-4-6JjlDwB1vN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59811-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59811 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|4.8.4 |4.8.5 --- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> --- GCC 4.8.4 has been released.
next prev parent reply other threads:[~2014-12-19 13:29 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-01-14 17:30 [Bug fortran/59811] New: Huge increase in memory usage and compile time with gfortran 4.8 bastian.feigl at kit dot edu 2014-01-15 12:06 ` [Bug rtl-optimization/59811] [4.8/4.9 Regression] " rguenth at gcc dot gnu.org 2014-01-15 13:53 ` [Bug rtl-optimization/59811] [4.8/4.9 Regression] Huge increase in memory usage and compile time in combine rguenth at gcc dot gnu.org 2014-01-22 15:01 ` jakub at gcc dot gnu.org 2014-01-22 15:16 ` jakub at gcc dot gnu.org 2014-01-31 11:35 ` rguenth at gcc dot gnu.org 2014-01-31 11:41 ` jakub at gcc dot gnu.org 2014-01-31 11:48 ` rguenther at suse dot de 2014-05-22 9:02 ` [Bug rtl-optimization/59811] [4.8/4.9/4.10 " rguenth at gcc dot gnu.org 2014-12-19 13:29 ` jakub at gcc dot gnu.org [this message] 2015-06-23 8:23 ` [Bug rtl-optimization/59811] [4.8/4.9/5/6 " rguenth at gcc dot gnu.org 2015-06-26 19:59 ` [Bug rtl-optimization/59811] [4.9/5/6 " jakub at gcc dot gnu.org 2015-06-26 20:30 ` 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-59811-4-6JjlDwB1vN@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).