From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Craig Silverstein <csilvers@google.com>,
drow@false.org, bauerman@br.ibm.com
Subject: Re: Patch to handle compressed sections
Date: Thu, 03 Apr 2008 11:01:00 -0000 [thread overview]
Message-ID: <200804031145.04476.pedro@codesourcery.com> (raw)
In-Reply-To: <20080403064309.5454D3F25F0@localhost>
A Thursday 03 April 2008 07:43:09, Craig Silverstein wrote:
> I'm sorry to do this, but hot on the heels of my last patch comes a
> new version. While trying to implement this in gold, I realized that
> gold does not have endianness information handy at the time it's
> writing the compressed header.
> So I've changed back to writing the
> uncompressed size always in big-endian. New patch below.
>
Out of curiosity, did you try running the whole GDB testsuite
outputting compressed debug info? Perhaps with
"set GDBFLAGS=\"-Wl,--whatever-switch-is-necessary\"" in your
site.exp?
--
Pedro Alves
next prev parent reply other threads:[~2008-04-03 10:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-25 23:05 Craig Silverstein
2008-03-26 16:10 ` Thiago Jung Bauermann
2008-03-26 17:40 ` Craig Silverstein
2008-03-26 18:01 ` Daniel Jacobowitz
2008-03-26 18:36 ` Craig Silverstein
2008-04-01 14:28 ` Daniel Jacobowitz
2008-04-02 0:38 ` Craig Silverstein
2008-04-02 12:27 ` Daniel Jacobowitz
2008-04-02 12:51 ` Craig Silverstein
2008-04-02 14:13 ` Andreas Schwab
2008-04-03 7:38 ` Craig Silverstein
2008-04-03 8:45 ` Craig Silverstein
2008-04-03 11:01 ` Pedro Alves [this message]
2008-04-03 11:10 ` Pedro Alves
2008-04-03 21:43 ` Craig Silverstein
2008-04-04 1:28 ` Craig Silverstein
2008-04-15 6:16 ` Craig Silverstein
2008-04-17 16:24 ` Daniel Jacobowitz
2008-04-17 20:57 ` Craig Silverstein
2008-04-17 21:09 ` Daniel Jacobowitz
2008-04-19 0:32 ` Craig Silverstein
2008-04-19 0:13 ` Daniel Jacobowitz
2008-04-19 0:32 ` Daniel Jacobowitz
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=200804031145.04476.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=bauerman@br.ibm.com \
--cc=csilvers@google.com \
--cc=drow@false.org \
--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