public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Mike Frysinger <vapier@gentoo.org>
Cc: jose.marchesi@oracle.com, simark@simark.ca,
	indu.bhagat@oracle.com, gdb-patches@sourceware.org,
	elena.zannoni@oracle.com
Subject: Re: [PATCH] gdb: link executables with libtool
Date: Sun, 06 Nov 2022 08:22:03 +0200	[thread overview]
Message-ID: <83a65438ms.fsf@gnu.org> (raw)
In-Reply-To: <Y2cgGo/zm2fUFnw3@vapier> (message from Mike Frysinger via Gdb-patches on Sun, 6 Nov 2022 09:46:50 +0700)

> Date: Sun, 6 Nov 2022 09:46:50 +0700
> From: Mike Frysinger via Gdb-patches <gdb-patches@sourceware.org>
> Cc: Simon Marchi <simark@simark.ca>, indu.bhagat@oracle.com,
>  gdb-patches@sourceware.org, elena.zannoni@oracle.com
> 
> > The SFrame support (it is a frame unwinding format) is purely in
> > binutils (assembler, and linker via BFD) and, per-se, it doesn't concern
> > GDB at all.
> 
> is it really a big deal to wait for the GDB 13 branch to be cut ?  with
> binutils-2.39 being recentlyish released, it's not like binutils-2.40 is
> coming out any time soon.  further, afaict, the sframe patchset hasn't
> finished review even on the binutils side.

Based on history, I'd expect Binutils 2.40 around February.

      parent reply	other threads:[~2022-11-06  6:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-05 13:08 Jose E. Marchesi
2022-11-05 13:26 ` Eli Zaretskii
2022-11-05 14:30   ` Jose E. Marchesi
2022-11-05 16:40     ` Simon Marchi
2022-11-05 18:04       ` Jose E. Marchesi
2022-11-06  0:57         ` Simon Marchi
2022-11-06  2:46         ` Mike Frysinger
2022-11-06  5:57           ` Indu Bhagat
2022-11-06  6:22           ` Eli Zaretskii [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=83a65438ms.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=elena.zannoni@oracle.com \
    --cc=gdb-patches@sourceware.org \
    --cc=indu.bhagat@oracle.com \
    --cc=jose.marchesi@oracle.com \
    --cc=simark@simark.ca \
    --cc=vapier@gentoo.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).