From: csilvers@google.com (Craig Silverstein)
To: drow@false.org
Cc: bauerman@br.ibm.com, gdb-patches@sourceware.org
Subject: Re: Patch to handle compressed sections
Date: Thu, 17 Apr 2008 20:57:00 -0000 [thread overview]
Message-ID: <20080417185752.244673F23EF@localhost> (raw)
In-Reply-To: <20080417161526.GF17488@caradoc.them.org> (message from Daniel Jacobowitz on Thu, 17 Apr 2008 12:15:26 -0400)
} Space before parenthesis.
Doh, and I was so careful looking for all of those!
} You can use bfd_getb64.
Yeah, we had some debate about that internally. The issue is that
bfd_getb64 crashes on machines without a 64-bit int type. That seemed
unnecessarily harsh here, especially since in practice section sizes
will never be longer than 32 bits.
Do you feel that strongly about it? I'd be more comfortable with code
that didn't make 32-bit assumptions. I can comment it if that will
help.
} Use the sourceware.org URL instead, please.
Sure thing.
} Do you have write access? If not, request it using the sourceware
} form - if you have write access to binutils then you already do.
I don't have write access. I've requested it.
} The other things needed for this feature are, IMO:
Makes sense to me. Should that be part of this patch, or is it ok to
do it in a followup patch?
} The other thing I very much want is an objcopy option to compress
} DWARF sections, but that's clearly beyond the call of duty. That
} will let GNU ld users take advantage of this and is probably easier
} than teaching GNU ld to compress .debug_info (though that would be
} nice, too).
Makes sense. Further plans, if we ever get around to it, include
adding support to readelf, objdump, and addr2line, and adding support
to as to generate compressed sections in .o files (obviously, this
will require a linker that knows how to deal with that, so it's a
longer-term plan). I'll add objcopy to the list.
craig
next prev parent reply other threads:[~2008-04-17 18:58 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
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 [this message]
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=20080417185752.244673F23EF@localhost \
--to=csilvers@google.com \
--cc=bauerman@br.ibm.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