public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "steven at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/40735] [4.3/4.4 regression] memory hog compiling big functions with -fPIE Date: Wed, 15 Jul 2009 07:34:00 -0000 [thread overview] Message-ID: <20090715073432.1173.qmail@sourceware.org> (raw) In-Reply-To: <bug-40735-11764@http.gcc.gnu.org/bugzilla/> ------- Comment #8 from steven at gcc dot gnu dot org 2009-07-15 07:34 ------- Does seem to be a real issue, somewhere. When trunk builds again, can you please give it a try too? -- steven at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last reconfirmed|0000-00-00 00:00:00 |2009-07-15 07:34:32 date| | Target Milestone|--- |4.3.5 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40735
next prev parent reply other threads:[~2009-07-15 7:34 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-07-13 19:37 [Bug target/40735] New: " doko at ubuntu dot com 2009-07-13 19:37 ` [Bug target/40735] " doko at ubuntu dot com 2009-07-14 9:21 ` rguenth at gcc dot gnu dot org 2009-07-14 10:31 ` doko at ubuntu dot com 2009-07-14 11:31 ` rguenth at gcc dot gnu dot org 2009-07-14 23:07 ` mikpe at it dot uu dot se 2009-07-14 23:10 ` pinskia at gcc dot gnu dot org 2009-07-14 23:33 ` mikpe at it dot uu dot se 2009-07-15 7:34 ` steven at gcc dot gnu dot org [this message] 2009-07-15 9:44 ` rguenth at gcc dot gnu dot org 2009-07-16 18:33 ` mikpe at it dot uu dot se 2009-07-22 21:57 ` [Bug target/40735] [4.3/4.4/4.5 Regression] " rguenth at gcc dot gnu dot org 2009-08-04 12:51 ` rguenth at gcc dot gnu dot org 2010-05-22 18:33 ` [Bug target/40735] [4.3/4.4/4.5/4.6 " rguenth at gcc dot gnu dot 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=20090715073432.1173.qmail@sourceware.org \ --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).