Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org, gdb-patches@sources.redhat.com
Subject: Re: add support for `S´ augmentation in dwarf2 debug  info
Date: Sat, 04 Mar 2006 18:01:00 -0000	[thread overview]
Message-ID: <20060304150719.GD20187@nevyn.them.org> (raw)
In-Reply-To: <orbqwnpne4.fsf@free.oliva.athome.lsd.ic.unicamp.br>

On Fri, Mar 03, 2006 at 12:18:43PM -0300, Alexandre Oliva wrote:
> This patch introduces code to recognize and take advantage of the "S"
> augmentation, but makes no effort to remove existing machine-specific
> code.  The testcase probably already worked without the change, but
> it's good to have it there to avoid regressions when someone decides
> to experiment with taking code out.

Is that enough justification for such a nasty testcase?  And it's going
to need more work over time; for instance, old assemblers or libgccs
will fail to build it, producing a noisy ERROR.


-- 
Daniel Jacobowitz
CodeSourcery


WARNING: multiple messages have this Message-ID
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org, gdb-patches@sources.redhat.com
Subject: Re: add support for `S´ augmentation in dwarf2 debug  info
Date: Mon, 06 Mar 2006 15:18:00 -0000	[thread overview]
Message-ID: <20060304150719.GD20187@nevyn.them.org> (raw)
Message-ID: <20060306151800.hEUQOygtdqCHRzXQ9NN9ebWrzOvS0BHxQOIsfBeUclI@z> (raw)
In-Reply-To: <orbqwnpne4.fsf@free.oliva.athome.lsd.ic.unicamp.br>

On Fri, Mar 03, 2006 at 12:18:43PM -0300, Alexandre Oliva wrote:
> This patch introduces code to recognize and take advantage of the "S"
> augmentation, but makes no effort to remove existing machine-specific
> code.  The testcase probably already worked without the change, but
> it's good to have it there to avoid regressions when someone decides
> to experiment with taking code out.

Is that enough justification for such a nasty testcase?  And it's going
to need more work over time; for instance, old assemblers or libgccs
will fail to build it, producing a noisy ERROR.


-- 
Daniel Jacobowitz
CodeSourcery


  parent reply	other threads:[~2006-03-04 15:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-03 17:41 Alexandre Oliva
2006-03-04 12:05 ` Mark Kettenis
2006-03-04 14:54   ` Alexandre Oliva
2006-03-04 18:01 ` Daniel Jacobowitz [this message]
2006-03-06 15:18   ` Daniel Jacobowitz
2006-03-07 14:21   ` Alexandre Oliva
2006-03-29  0:04     ` Daniel Jacobowitz
2006-05-28  6:42       ` Alexandre Oliva

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=20060304150719.GD20187@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=gdb-patches@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