From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@redhat.com>
Cc: brobecker@adacore.com, pmuldoon@redhat.com, gdb@sourceware.org
Subject: Re: py-breakpoint.c fails to compile with MinGW GCC
Date: Thu, 28 Jul 2011 16:17:00 -0000 [thread overview]
Message-ID: <83livie5x7.fsf@gnu.org> (raw)
In-Reply-To: <m34o2676m8.fsf@fleche.redhat.com>
> From: Tom Tromey <tromey@redhat.com>
> Cc: pmuldoon@redhat.com, Eli Zaretskii <eliz@gnu.org>, gdb@sourceware.org
> Date: Thu, 28 Jul 2011 09:43:59 -0600
>
> Or, just require people to use a newer GCC; 3.4 is 5 years old at
> this point.
Just to clarify: I never upgraded my GCC because the existing 4.x
series (a) produce code that is less debug-friendly under any non-zero
optimization level, (b) some versions are buggy (e.g., 4.5), and
(c) is slower. Paying compilation time penalty without any visible
gains seemed unwise, especially since my main development machine runs
on 6-year-old hardware.
I will probably upgrade when 4.7 is released, because I understand it
will be more debug-friendly.
next prev parent reply other threads:[~2011-07-28 16:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 12:07 Eli Zaretskii
2011-07-28 14:54 ` Phil Muldoon
2011-07-28 15:01 ` Tom Tromey
2011-07-28 15:19 ` Joel Brobecker
2011-07-28 15:37 ` Phil Muldoon
2011-07-28 15:44 ` Tom Tromey
2011-07-28 16:11 ` Kai Tietz
2011-07-28 16:17 ` Eli Zaretskii [this message]
2011-07-28 16:46 ` Tom Tromey
2011-07-28 17:07 ` Eli Zaretskii
2011-07-29 3:04 ` Chris Sutcliffe
2011-07-29 6:13 ` Eli Zaretskii
2011-07-28 16:13 ` Eli Zaretskii
2011-07-28 16:25 ` Joel Brobecker
2011-07-28 16:48 ` Tom Tromey
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=83livie5x7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=pmuldoon@redhat.com \
--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