From: Ben Longbons <brlongbons@gmail.com>
To: Michael Veksler <mveksler@tx.technion.ac.il>
Cc: Andrew Pinski <pinskia@gmail.com>, GDB Development <gdb@sourceware.org>
Subject: Re: [C++] System Requirements
Date: Wed, 18 Dec 2013 19:16:00 -0000 [thread overview]
Message-ID: <CA+XNFZNfeGuaSfQR22DpW6GMY1ywoR+S+b5VEWqhFz117Q2j3Q@mail.gmail.com> (raw)
In-Reply-To: <52B1993F.9030105@tx.technion.ac.il>
On Wed, Dec 18, 2013 at 4:46 AM, Michael Veksler
<mveksler@tx.technion.ac.il> wrote:
> Nevertheless, supporting pre-gcc-3.4 compilers is still a pain.
> Not only because language semantics is different (two-phase
> name lookup in templates vs. one) but because you can't easily
> build old compilers on modern machines. And if you don't test
> your code with a pre-gcc-3.4 then your code won't work with
> earlier compilers.
Right. And my point is that not enough people use a pre-4.1 compiler
either, even though 3.4 is *supposed* to mark the beginning of
compliance.
I'm definitely not happy about 4.1 - it would make gdb code
significantly worse than it could be - but at least I can be confident
that there is a userbase from RHEL 5.
-Ben
next prev parent reply other threads:[~2013-12-18 19:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-14 0:34 Ben Longbons
2013-12-14 0:40 ` Ben Longbons
2013-12-15 12:28 ` Michael Veksler
2013-12-17 2:29 ` Andrew Pinski
2013-12-17 4:02 ` Ben Longbons
2013-12-18 12:47 ` Michael Veksler
2013-12-18 19:16 ` Ben Longbons [this message]
2013-12-15 15:31 ` Jan Kratochvil
2013-12-15 17:04 ` Ben Longbons
2013-12-15 19:53 ` Mark Kettenis
2013-12-16 13:03 ` Ivo Raisr
2013-12-16 13:52 ` Phi Debian
2013-12-17 5:35 ` Sergio Durigan Junior
2013-12-16 19:10 ` Eli Zaretskii
2013-12-16 20:09 ` Ben Longbons
2013-12-16 19:05 ` Eli Zaretskii
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=CA+XNFZNfeGuaSfQR22DpW6GMY1ywoR+S+b5VEWqhFz117Q2j3Q@mail.gmail.com \
--to=brlongbons@gmail.com \
--cc=gdb@sourceware.org \
--cc=mveksler@tx.technion.ac.il \
--cc=pinskia@gmail.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