public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "emil at tywoniak dot eu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/83967] LTO removes C functions declared as weak in assembler(depending on files order in linking)
Date: Mon, 11 Jan 2021 14:36:56 +0000	[thread overview]
Message-ID: <bug-83967-4-BnQ1xl1aR6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-83967-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83967

--- Comment #19 from Emil Jiří Tywoniak <emil at tywoniak dot eu> ---
(In reply to Emil Jiří Tywoniak from comment #18)
> (In reply to Christophe Lyon from comment #17)
> > Any chance you can try with a toolchain using binutils-2.35?
> > 
> > As I indicated in https://bugs.launchpad.net/gcc-arm-embedded/+bug/1747966
> > there's a related bug fix in binutils-2.35, but Arm's 2020-q2 toolchain
> > still uses 2.34.50.20200226.
> 
> Issue in my project is not present anymore with 2020 Q4 release, which packs
> GNU ld (GNU Arm Embedded Toolchain 10-2020-q4-major) 2.35.1.20201028. Will
> test example from Comment #11. My apologies for not reading threads more
> carefully

I have now tested the bad branch from Comment #11 and did not replicate the bug
with the Q4 toolchain (specifically, the Systick handler in .lst is exactly the
same as in the good branch excerpt in Comment #11)

      parent reply	other threads:[~2021-01-11 14:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-83967-4@http.gcc.gnu.org/bugzilla/>
2021-01-07 10:22 ` emil at tywoniak dot eu
2021-01-08 13:59 ` clyon at gcc dot gnu.org
2021-01-11 14:23 ` emil at tywoniak dot eu
2021-01-11 14:36 ` emil at tywoniak dot eu [this message]

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=bug-83967-4-BnQ1xl1aR6@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).