From: "H.J. Lu" <hjl.tools@gmail.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Richard Biener <richard.guenther@gmail.com>,
Jan Hubicka <hubicka@ucw.cz>
Subject: Re: [PATCH][RFC] API extension for binutils (type of symbols).
Date: Mon, 9 Mar 2020 11:25:11 -0700 [thread overview]
Message-ID: <CAMe9rOrscmBCQqCf9ab=3jg1NbUNUWS-P=QQvG_pZQNc18itLw@mail.gmail.com> (raw)
In-Reply-To: <4be8dd93-35cf-3155-2843-87a56fb774d9@suse.cz>
On Mon, Mar 9, 2020 at 9:56 AM Martin Liška <mliska@suse.cz> wrote:
>
> On 3/9/20 4:36 PM, H.J. Lu wrote:
> > We nee to support different variables, like TLS, data and bss variables.
>
> Why do we need TLS? Right now, it's not supported by nm. Or am I wrong?
Since you are introducing symbol types, why not support TLS?
> About BSS and DATA I agree that it would be handy. I can theoretically
> covered with code in get_variable_section/bss_initializer_p. But it's
> quite logic and I'm not sure we should simulate it.
>
> @Honza/Richi: Do you have any opinion about that?
>
> Thanks,
> Martin
--
H.J.
next prev parent reply other threads:[~2020-03-09 18:25 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 9:30 Martin Liška
2020-03-09 15:36 ` H.J. Lu
2020-03-09 16:56 ` Martin Liška
2020-03-09 18:25 ` H.J. Lu [this message]
2020-03-09 20:19 ` Jan Hubicka
2020-03-10 10:05 ` Martin Liška
2020-03-10 10:49 ` Richard Biener
2020-03-10 11:09 ` Jan Hubicka
2020-03-10 11:24 ` Richard Biener
2020-03-10 12:07 ` Martin Liška
2020-03-11 9:19 ` Martin Liška
2020-03-11 10:22 ` Richard Biener
2020-03-11 10:30 ` Richard Biener
2020-03-11 12:22 ` Martin Liška
2020-03-11 12:51 ` Richard Biener
2020-03-11 13:07 ` Martin Liška
2020-03-11 13:24 ` H.J. Lu
2020-03-11 13:28 ` Martin Liška
2020-03-11 14:16 ` Alexander Monakov
2020-03-11 14:15 ` Martin Liška
2020-03-12 10:36 ` Strange read for simple_object_elf_find_sections for .a file Martin Liška
2020-03-12 10:39 ` Martin Liška
2020-03-12 12:32 ` [PATCH][RFC] API extension for binutils (type of symbols) Martin Liška
2020-03-12 12:55 ` Jan Hubicka
2020-03-12 13:10 ` Martin Liška
2020-03-12 13:15 ` Richard Biener
2020-03-12 13:24 ` Martin Liška
2020-03-12 13:31 ` Martin Liška
2020-03-16 11:12 ` H.J. Lu
2020-03-16 13:50 ` Martin Liška
2020-03-16 14:34 ` H.J. Lu
2020-03-16 14:38 ` Martin Liška
2020-03-17 23:27 ` Jan Hubicka
2020-03-18 8:52 ` Martin Liška
2020-03-18 8:53 ` [PATCH] Bump LTO bytecode version Martin Liška
2020-03-18 8:56 ` Richard Biener
2020-03-18 9:00 ` Martin Liška
2020-03-18 9:34 ` Richard Biener
2020-03-18 10:20 ` Martin Liška
2020-03-19 9:12 ` [PATCH][RFC] API extension for binutils (type of symbols) Richard Biener
2020-03-19 15:00 ` Martin Liška
2020-03-19 15:46 ` Richard Biener
2020-03-19 15:50 ` H.J. Lu
2020-03-19 16:00 ` Martin Liška
2020-03-19 16:51 ` H.J. Lu
2020-03-19 19:56 ` Richard Biener
2020-03-19 20:07 ` H.J. Lu
2020-03-09 19:45 ` Michael Matz
2020-03-10 9:39 ` Martin Liška
2020-03-10 12:20 ` Martin Liška
2020-03-10 14:26 ` Michael Matz
2020-03-26 16:54 ` Jeff Law
2020-03-27 9:10 ` Martin Liška
2020-03-27 14:21 ` Jeff Law
2020-03-27 15:21 ` Martin Liška
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='CAMe9rOrscmBCQqCf9ab=3jg1NbUNUWS-P=QQvG_pZQNc18itLw@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=mliska@suse.cz \
--cc=richard.guenther@gmail.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).