public inbox for archer@sourceware.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Dodji Seketeli <dodji@redhat.com>,
	Project Archer <archer@sourceware.org>
Subject: Re: Fedora 14 debug proposal
Date: Mon, 14 Jun 2010 10:17:00 -0000	[thread overview]
Message-ID: <20100611194740.GD7811@tyan-ft48-01.lab.bos.redhat.com> (raw)
In-Reply-To: <m3k4q548gf.fsf@fleche.redhat.com>

On Fri, Jun 11, 2010 at 02:31:44PM -0600, Tom Tromey wrote:
> >>>>> "Tom" == Tom Tromey <tromey@redhat.com> writes:
> 
> Dodji> I guess at worst, upstream will require a flag to get the
> Dodji> .debug_{pug,aranges,pubnames,pubtypes} section back for a little
> Dodji> while before removing the code completely?
> 
> Tom> I wouldn't bother with an option, but then I'm not very concerned about
> Tom> whether this particular change goes upstream.  Of course, that is easy
> Tom> for me to say -- I will do whatever Jakub thinks is best here.
> 
> On irc, Jakub asked for this to be sent upstream, just to see if they
> would accept it.  I'm struggling through a regtest, you'll see it on
> gcc-patches "soon".

I guess everybody is struggling with bootstraps/regtests lately,
apparently every second patch or so from Honza lately causes a bootstrap failure
or some regression, really wonder what kind of testing he does on his
patches if any.

	Jakub

  reply	other threads:[~2010-06-14 10:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-08 20:38 Tom Tromey
2010-06-09 13:54 ` Dodji Seketeli
2010-06-09 16:11   ` Tom Tromey
2010-06-11 20:31     ` Tom Tromey
2010-06-14 10:17       ` Jakub Jelinek [this message]
2010-06-11 20:39         ` Tom Tromey
2010-06-11 20:33 ` Tom Tromey
2010-06-13 10:40 ` Roland McGrath
2010-06-14 20:06   ` Tom Tromey
2010-06-15 19:46   ` Tom Tromey
2010-06-15 22:26     ` Roland McGrath

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=20100611194740.GD7811@tyan-ft48-01.lab.bos.redhat.com \
    --to=jakub@redhat.com \
    --cc=archer@sourceware.org \
    --cc=dodji@redhat.com \
    --cc=tromey@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).