From: Joel Sherrill <joel.sherrill@oarcorp.com>
To: Andrew Pinski <pinskia@gmail.com>,Joel Brobecker <brobecker@adacore.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: GDB dropping support for mips-irix and alpha-tru64
Date: Fri, 12 Sep 2014 01:11:00 -0000 [thread overview]
Message-ID: <a675c2f1-f6fe-401e-bfe0-a6d7d6a0da47@email.android.com> (raw)
In-Reply-To: <CA+=Sn1=0FPr+53L3fwggSdBZyM+PdomJj3PcsoBJsDTeA2J3GA@mail.gmail.com>
Thanks for the quick responses. Sounds like the final cruft to remove.
--joel
On September 11, 2014 8:32:54 PM EDT, Andrew Pinski <pinskia@gmail.com> wrote:
>On Thu, Sep 11, 2014 at 5:30 PM, Joel Brobecker <brobecker@adacore.com>
>wrote:
>>> First I am not complaining but just have a couple of clarifying
>questions.
>>>
>>> + does this include binutils and/or GCC?
>>
>> No, this only is about the GDB part of the code.
>
>GCC support for IRIX was already removed a few years ago.
>
>Thanks,
>Andrew
>
>>
>>> + does this have the side-effect of impacting any embedded mips
>>> targets? I expect not.
>>
>> No. For MIPS, this should only affect native IRIX support.
>>
>> --
>> Joel
next prev parent reply other threads:[~2014-09-12 1:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 18:52 Joel Brobecker
2014-09-11 20:53 ` Joel Sherrill
2014-09-12 0:30 ` Joel Brobecker
2014-09-12 0:33 ` Andrew Pinski
2014-09-12 1:11 ` Joel Sherrill [this message]
2014-09-12 9:53 ` Matthew Fortune
2014-10-11 14:36 ` VAX Ultrix? (Re: GDB dropping support for mips-irix and alpha-tru64) Pedro Alves
2014-10-13 13:38 ` Joel Brobecker
2014-10-13 13:57 ` Maciej W. Rozycki
2014-10-13 15:02 ` Pedro Alves
2014-10-13 16:04 ` Mark Kettenis
2014-10-15 13:22 ` Pedro Alves
2014-10-17 13:47 ` GDB is removing VAX Ultrix support Pedro Alves
2014-10-24 17:12 ` Support for VAX Ultrix removed Pedro Alves
2014-10-24 17:11 ` GDB dropping support for mips-irix and alpha-tru64 Pedro Alves
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=a675c2f1-f6fe-401e-bfe0-a6d7d6a0da47@email.android.com \
--to=joel.sherrill@oarcorp.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--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