public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bero at arklinux dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/45364] Compiling wine's directx.c with -O1 -g takes a very long time Date: Sat, 21 Aug 2010 01:10:00 -0000 [thread overview] Message-ID: <20100821011025.5880.qmail@sourceware.org> (raw) In-Reply-To: <bug-45364-5606@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from bero at arklinux dot org 2010-08-21 01:10 ------- Assumed it was an infinite loop a bit too early -- it did finish after giving it some more time. There is a speed problem though. Updating summary and severity. -- bero at arklinux dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |enhancement Summary|Apparent infinite loop while|Compiling wine's directx.c |compiling wine's directx.c |with -O1 -g takes a very |with -O1 -g |long time http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45364
next prev parent reply other threads:[~2010-08-21 1:10 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-08-21 1:00 [Bug middle-end/45364] New: Apparent infinite loop while compiling wine's directx.c with -O1 -g bero at arklinux dot org 2010-08-21 1:01 ` [Bug middle-end/45364] " bero at arklinux dot org 2010-08-21 1:10 ` bero at arklinux dot org [this message] 2010-08-21 5:13 ` [Bug middle-end/45364] Compiling wine's directx.c with -O1 -g takes a very long time hjl dot tools at gmail dot com 2010-08-21 14:36 ` mikpe at it dot uu dot se 2010-08-21 15:45 ` mikpe at it dot uu dot se 2010-08-21 15:57 ` jakub at gcc dot gnu dot org [not found] <bug-45364-4@http.gcc.gnu.org/bugzilla/> 2012-02-02 17:36 ` pinskia at gcc dot gnu.org 2014-01-28 9:03 ` rguenth at gcc dot gnu.org 2014-01-28 13:14 ` rguenth 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=20100821011025.5880.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).