public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vlad at demoninsight dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/42159] app compiled with 4.4.2 SIGABRTs after a trivial nested throw/stack unwinding
Date: Sat, 28 Nov 2009 06:42:00 -0000	[thread overview]
Message-ID: <20091128064234.1891.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42159-18481@http.gcc.gnu.org/bugzilla/>



------- Comment #8 from vlad at demoninsight dot com  2009-11-28 06:42 -------
I am somewhat unsure about what our best course of action is at this point. Can
we discuss this in gnu forums? Could I help by providing diagnostics?

I'd like to use 4.4.x for its OpenMP support etc in preference to the xcode
version. I see that many (all?) prerequisites for building gcc are available
through fink: gmp, ppl, fmpr, etc. I wonder if I could leverage fink to get all
of the dependencies and then try building the current against those.

Jack, since you're the maintainer of the fink package you probably build it all
the time. Would be able to point in the right direction with the above idea,
assuming a vanilla fink install in /sw? I feel lost among the many svn branches
already...


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42159


  parent reply	other threads:[~2009-11-28  6:42 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-24  1:00 [Bug c++/42159] New: " vlad at demoninsight dot com
2009-11-24  1:25 ` [Bug c++/42159] " howarth at nitro dot med dot uc dot edu
2009-11-24  1:37 ` vlad at demoninsight dot com
2009-11-24 15:49 ` vlad at demoninsight dot com
2009-11-25 15:59 ` aufpasser at gmail dot com
2009-11-25 17:16 ` vlad at demoninsight dot com
2009-11-25 17:28 ` howarth at nitro dot med dot uc dot edu
2009-11-25 17:29 ` howarth at nitro dot med dot uc dot edu
2009-11-28  6:42 ` vlad at demoninsight dot com [this message]
2009-11-29 16:04 ` [Bug target/42159] " vlad at demoninsight dot com
2009-11-30 15:19 ` vlad at demoninsight dot com
2009-11-30 15:27 ` rguenth at gcc dot gnu dot org
2009-11-30 16:07 ` vlad at demoninsight dot com
2009-11-30 16:47 ` redi at gcc dot gnu dot org
2009-12-01  5:50 ` vlad at demoninsight dot com
2009-12-31 17:42 ` [Bug target/42159] [4.4 only] " simon at pushface dot org
2010-05-18 10:29 ` [Bug target/42159] [4.4/4.5/4.6] app " fxcoudert at gcc dot gnu dot org
2010-05-19 22:06 ` simon at pushface dot org
2010-06-06 19:33 ` michael at jarvis dot net
2010-07-15 16:58 ` pinskia at gcc dot gnu dot org
2010-07-15 16:59 ` pinskia at gcc dot gnu dot org
2010-07-15 16:59 ` pinskia at gcc dot gnu dot org
2010-07-15 17:03 ` redi 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=20091128064234.1891.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: link
Be 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).