From: JonY <jon_y@users.sourceforge.net>
To: gcc-help@gcc.gnu.org
Subject: Re: trunk build error after revision 189603
Date: Wed, 22 Aug 2012 11:11:00 -0000 [thread overview]
Message-ID: <5034A086.8000406@users.sourceforge.net> (raw)
In-Reply-To: <CAMPTgK28PDywtKHCswPg-L6=-W6DBsdQBU-VmXzZVWvpKOrgZg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 264 bytes --]
On 8/21/2012 23:30, niXman wrote:
> 2012/8/21 JonY:
>> --with-dwarf2
>
> Using dwarf I just going to succeed.
> But I was interested the build using SJLJ.
>
>
That is a debug format, not EH. stabs doesn't cut it anymore for large
C++ codebases.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 196 bytes --]
next prev parent reply other threads:[~2012-08-22 9:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 3:18 niXman
2012-08-20 5:47 ` JonY
2012-08-20 13:25 ` niXman
2012-08-21 2:13 ` niXman
2012-08-21 10:02 ` JonY
2012-08-21 11:30 ` niXman
2012-08-21 13:35 ` JonY
2012-08-21 17:41 ` niXman
2012-08-22 11:11 ` JonY [this message]
2012-08-22 13:06 ` niXman
2012-08-22 13:44 ` JonY
2012-09-05 9:15 ` niXman
2012-09-05 9:31 ` JonY
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=5034A086.8000406@users.sourceforge.net \
--to=jon_y@users.sourceforge.net \
--cc=gcc-help@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).