From: Jakub Jelinek <jakub@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Michael Matz <matz@suse.de>, Diego Novillo <dnovillo@google.com>,
Richard Guenther <rguenther@suse.de>,
gcc-patches@gcc.gnu.org, Lawrence Crowl <crowl@google.com>,
bonzini@gnu.org, dj@redhat.com, tromey@redhat.com,
laurynas.biveinis@gmail.com, gdb@sourceware.org
Subject: Re: Merge C++ conversion into trunk (0/6 - Overview)
Date: Wed, 15 Aug 2012 16:39:00 -0000 [thread overview]
Message-ID: <20120815163758.GF1999@tucnak.redhat.com> (raw)
In-Reply-To: <20120815154934.GA2709@host2.jankratochvil.net>
On Wed, Aug 15, 2012 at 05:49:34PM +0200, Jan Kratochvil wrote:
> On Wed, 15 Aug 2012 17:44:32 +0200, Michael Matz wrote:
> > On Wed, 15 Aug 2012, Jan Kratochvil wrote:
> > It's not needless as the examples here show. gdb is about helping people
> > debug their stuff, not about language lawyering.
>
> In such case there should be a GDB setting for it as at least from my opinion
> it complicates the debugging. Then there may be different opinions what
> should be the default.
That would be fine for gcc development purposes. We could switch that mode
on at the end of gcc .gdbinit .
Jakub
next prev parent reply other threads:[~2012-08-15 16:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120812200427.GA12561@google.com>
2012-08-15 12:01 ` Richard Guenther
2012-08-15 12:19 ` Diego Novillo
2012-08-15 12:21 ` Richard Guenther
2012-08-15 12:23 ` Diego Novillo
2012-08-15 15:13 ` Jan Kratochvil
2012-08-15 15:44 ` Michael Matz
2012-08-15 15:50 ` Jan Kratochvil
2012-08-15 16:39 ` Jakub Jelinek [this message]
2012-08-15 16:00 ` Diego Novillo
2012-08-15 17:54 ` Tom Tromey
2012-08-15 18:02 ` Gabriel Dos Reis
2012-08-15 18:21 ` Tom Tromey
2012-08-15 18:26 ` Gabriel Dos Reis
2012-08-17 17:45 ` Keith Seitz
2012-08-17 17:56 ` H.J. Lu
2012-08-15 14:25 ` Mike Stump
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=20120815163758.GF1999@tucnak.redhat.com \
--to=jakub@redhat.com \
--cc=bonzini@gnu.org \
--cc=crowl@google.com \
--cc=dj@redhat.com \
--cc=dnovillo@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=laurynas.biveinis@gmail.com \
--cc=matz@suse.de \
--cc=rguenther@suse.de \
--cc=tromey@redhat.com \
/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).