From: Georg-Johann Lay <avr@gjlay.de>
To: "Martin Liška" <mliska@suse.cz>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Do not emit __gnu_lto_v1 symbol.
Date: Wed, 31 Jul 2019 14:15:00 -0000 [thread overview]
Message-ID: <5D419DDD.9090500@gjlay.de> (raw)
In-Reply-To: <3f0e3ac1-a858-2b07-30bd-45286fd7fe98@suse.cz>
Martin Liška schrieb:
> On 7/29/19 3:46 PM, Georg-Johann Lay wrote:
>> Hi Martin.
>>
>> In SVN r273662 you changed a comment in avr.c from __gnu_lto_v1 to __gnu_lto_slim without changing the relevant code:
>
> Yes.
>
>> /* __gnu_lto_slim is just a marker for the linker injected by toplev.c.
>> There is no need to trigger __do_clear_bss code for them. */
>>
>> if (!STR_PREFIX_P (name, "__gnu_lto"))
>> avr_need_clear_bss_p = true;
>
> Because now, the only symbol that starts with __gnu_lto is __gnu_lto_slim. That's why I adjusted
> the comment only to reflect reality.
Oops, sorry for the noise. Must have had a glitch in my eyes...
Johann
next prev parent reply other threads:[~2019-07-31 13:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 14:03 Georg-Johann Lay
2019-07-30 8:07 ` Martin Liška
2019-07-31 14:15 ` Georg-Johann Lay [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-07-15 13:47 Martin Liška
2019-07-21 20:06 ` Jeff Law
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=5D419DDD.9090500@gjlay.de \
--to=avr@gjlay.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=mliska@suse.cz \
/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).