From: Martin Uecker <uecker@eecs.berkeley.edu>
To: gcc@gcc.gnu.org
Subject: debug strings output order is arbitrary
Date: Sun, 16 Mar 2014 02:58:00 -0000 [thread overview]
Message-ID: <20140315195827.340527e6@lemur> (raw)
Hi list,
the strings in the ".debug_str" section are output
in an arbitrary order. Could this be changed?
The function 'output_indirect_strings' in 'gcc/dwarf2out.c'
uses htab_traverse which then outputs the string in the
order they appear in the hash table. Instead, it would
be nicer to output them based on their labels (which are
assigned based on the order of creation).
This would minimize differences between builds with
slightly different build environments, e.g. directory.
Martin
next reply other threads:[~2014-03-16 2:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-16 2:58 Martin Uecker [this message]
2014-03-17 8:44 ` Richard Biener
2014-03-17 21:01 ` Martin Uecker
2014-03-18 9:04 ` Richard Biener
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=20140315195827.340527e6@lemur \
--to=uecker@eecs.berkeley.edu \
--cc=gcc@gcc.gnu.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).