Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: Obsoleting Solaris 10 support
Date: Wed, 17 Oct 2018 12:34:00 -0000	[thread overview]
Message-ID: <yddzhvcg3bh.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <20181016163907.GF17534@adacore.com> (Joel Brobecker's message of	"Tue, 16 Oct 2018 09:39:07 -0700")

Hi Joel,

>> this would argue for an obsoletion in the GDB 8.4 timeframe, roughly at
>> the same time GCC itself does.  Issues I'm facing with Solaris 10 right
>> now (apart from the S10-only build breakages) are having to deal with
>> different syscall numbers while working on an xml syscall table for
>> Solaris and catch syscall support, as well as differences in corefile
>> contents.  I suspect there will be more as time goes on.
>
> Sound good. Feel free to step in and make suggestions if you have
> new info that makes you think we should stop support earlier.

I guess 8.4 should be fine.  I've just checked the last couple of
releases which suggest that 8.3 will be ready sometime next spring,
close to the gcc 9 release.  In that case, obsoletion/removal in gdb 8.4
is just fine.  Initially I'd misremembered that gdb followed a procedure
similar to gcc (obsoletion in one release, removal in the next), but the
two being almost one step isn't a problem either.

	Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University


  parent reply	other threads:[~2018-10-17 12:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-16  9:42 Rainer Orth
2018-10-16 14:20 ` Joel Brobecker
2018-10-16 14:31   ` Rainer Orth
2018-10-16 16:39     ` Joel Brobecker
2018-10-16 18:21       ` Dennis Clarke
2018-10-17 12:39         ` Rainer Orth
2018-10-17 12:34       ` Rainer Orth [this message]
2018-10-16 18:41 ` Dennis Clarke
2018-10-17 12:42   ` Rainer Orth

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=yddzhvcg3bh.fsf@CeBiTec.Uni-Bielefeld.DE \
    --to=ro@cebitec.uni-bielefeld.de \
    --cc=brobecker@adacore.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