Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Joel Sherrill <joel.sherrill@oarcorp.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] configure.tgt (x86_64-*-elf*): Remove i386bsd-tdep.o.
Date: Mon, 07 Nov 2016 21:18:00 -0000	[thread overview]
Message-ID: <CADPb22S4mnx0vW0s-Z-KNvntmVvqSUaFoVRrZ22KxWFh_gKSJA@mail.gmail.com> (raw)
In-Reply-To: <87296F42-C36A-408C-827E-BD00C03A8744@oarcorp.com>

On Wed, Nov 2, 2016 at 4:56 PM, Joel Sherrill <joel.sherrill@oarcorp.com> wrote:
> Please fix it as you see fit.
>
> You probably remember that all RTEMS targets for gdb and binutils are the same as the elf ones. No intention of adding an OS dependency.
>
> --joel
>
> On November 2, 2016 6:43:24 PM CDT, Doug Evans <dje@google.com> wrote:
>>Hi.
>>
>>This is just a cleanup.
>>I suppose there's the possibility of someone using x86_64-elf with bsd
>>but anything-elf is not supposed to have os-specific stuff like this.
>>
>>Any objections?
>>
>>For reference sake, it was added here.
>>I have no opinion on what to do for rtems so I kept things as is there.
>>Maybe when this was added it was just easier to lot x86_64-rtems
>>together
>>with x86_64-elf?
>>I couldn't find an email thread, but just likely missed it.
>>
>>commit f73dbb0e48ef50d2743fed89b68530b731329f05
>>Author: Joel Sherrill <joel.sherrill@oarcorp.com>
>>Date:   Fri Apr 3 19:08:27 2015 -0500
>>
>>     Add x86_64-*-rtems* target
>>
>>       ld/configure.tgt: Also add stanza for x86_64-*-elf.

Committed, thanks.


      reply	other threads:[~2016-11-07 21:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-02 23:43 Doug Evans
2016-11-02 23:56 ` Joel Sherrill
2016-11-07 21:18   ` Doug Evans [this message]

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=CADPb22S4mnx0vW0s-Z-KNvntmVvqSUaFoVRrZ22KxWFh_gKSJA@mail.gmail.com \
    --to=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=joel.sherrill@oarcorp.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