public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "doko at ubuntu dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/42093] New: bootstrap hangs in stage2 run of build/gengtype Date: Wed, 18 Nov 2009 15:29:00 -0000 [thread overview] Message-ID: <bug-42093-11764@http.gcc.gnu.org/bugzilla/> (raw) trunk 20091117 configured with --with-arch=armv7-a --with-mode=thumb --with-float=softfp --with-fpu=vfp hangs in the stage2 run of build/gengtype with 100% cpu time attaching to the running process: (gdb) bt #0 0x00029fb4 in ?? () #1 0x0000a4a8 in walk_type () #2 0x0000a4a8 in walk_type () Backtrace stopped: previous frame identical to this frame (corrupt stack?) -- Summary: bootstrap hangs in stage2 run of build/gengtype Product: gcc Version: 4.5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: doko at ubuntu dot com GCC target triplet: arm-linux-gnueabi http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42093
next reply other threads:[~2009-11-18 15:29 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-11-18 15:29 doko at ubuntu dot com [this message] 2009-11-19 4:12 ` [Bug bootstrap/42093] " doko at ubuntu dot com 2009-11-20 16:00 ` ramana at gcc dot gnu dot org 2009-12-11 10:18 ` ramana at gcc dot gnu dot org 2009-12-14 23:43 ` ramana at gcc dot gnu dot org 2009-12-16 11:11 ` [Bug bootstrap/42093] [4.5 regression] " ramana at gcc dot gnu dot org 2009-12-22 16:36 ` ramana at gcc dot gnu dot org 2009-12-23 16:37 ` ramana at gcc dot gnu dot org 2009-12-24 10:18 ` [Bug target/42093] [4.5 regression] Compressed switch tables for Thumb2 have signed offsets ramana at gcc dot gnu dot org 2010-06-07 21:00 ` grosser 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=bug-42093-11764@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).