Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Veksler <mveksler@tx.technion.ac.il>
To: Ben Longbons <brlongbons@gmail.com>, gdb@sourceware.org
Subject: Re: [C++] System Requirements
Date: Sun, 15 Dec 2013 12:28:00 -0000	[thread overview]
Message-ID: <52ADA077.7020406@tx.technion.ac.il> (raw)
In-Reply-To: <CA+XNFZO14xGBFNF5oy1y4Ec+r8+5DGzM1ZkgNaY2qqbUC1aGkQ@mail.gmail.com>

On 14/12/13 02:40, Ben Longbons wrote:
> <snip>
> NetBSD 6.1.1 (2013-08-22): gcc 4.8.1
> NetBSD 5.1 (2010-11-19): gcc 3.3.6
>
> OpenBSD 5.4 (2013-11-01): gcc 4.2.1
> OpenBSD 4.7 (2010-05-19): gcc 3.3.5
>
>
I recommend to avoid gcc versions prior to gcc-3.4. Over a decade ago I 
had to port code from gcc-3.2 to gcc-3.4
without losing support for gcc-3.2. Even though the code was much 
smaller than gdb it was a pain to support
both versions in parallel:
1. gcc-3.2 has an old C++ parser and supports a dialect of C++ which 
predates ISO C++.
2. gcc-3.2 does not have namespace
3. Requires STL as a separate library
4. Containers of the STL libraries do not understand allocators, and 
can't be taught to due to limitations in old C++
5. Templates have significantly different semantics, and define a 
one-pass parsing (unlike 2 pass in ISO C++).

Avoid gcc-3.2

Michael


  reply	other threads:[~2013-12-15 12:28 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 [this message]
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
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=52ADA077.7020406@tx.technion.ac.il \
    --to=mveksler@tx.technion.ac.il \
    --cc=brlongbons@gmail.com \
    --cc=gdb@sourceware.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