From: Andreas Schwab <schwab@linux-m68k.org>
To: Richard Biener via Gcc <gcc@gcc.gnu.org>
Cc: Florian Weimer <fweimer@redhat.com>,
Richard Biener <richard.guenther@gmail.com>,
Jonathan Yong <10walls@gmail.com>, Jan Hubicka <hubicka@ucw.cz>,
Nathan Sidwell <nathan@acm.org>
Subject: Re: libgcov, fork, and mingw (and other targets without the full POSIX set)
Date: Fri, 01 Dec 2023 11:48:16 +0100 [thread overview]
Message-ID: <87il5idwr3.fsf@igel.home> (raw)
In-Reply-To: <CAFiYyc08h-jgE8=cOPGnP9NUVNtbr1EtES8TF1=cqrmentErSA@mail.gmail.com> (Richard Biener via Gcc's message of "Fri, 1 Dec 2023 10:09:42 +0100")
On Dez 01 2023, Richard Biener via Gcc wrote:
> Hmm, so why's it then referenced and not "GCed"?
This has nothing to do with garbage collection. It's just the way
libgcc avoids having too many source files. It would be exactly the
same if every function were in its own file.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2023-12-01 10:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 8:02 Florian Weimer
2023-12-01 8:19 ` Eli Zaretskii
2023-12-01 9:00 ` LIU Hao
2023-12-01 9:16 ` Alexander Monakov
2023-12-01 8:42 ` Richard Biener
2023-12-01 8:57 ` Florian Weimer
2023-12-01 9:09 ` Richard Biener
2023-12-01 9:23 ` LIU Hao
2023-12-01 9:23 ` Alexander Monakov
2023-12-01 10:48 ` Andreas Schwab [this message]
2023-12-01 12:03 ` Jan Hubicka
2023-12-01 12:09 ` Jakub Jelinek
2023-12-07 12:50 ` Mark Wielaard
2023-12-08 13:59 ` Florian Weimer
2023-12-10 9:27 ` LIU Hao
2023-12-11 6:48 ` Florian Weimer
2023-12-08 8:53 Julian Waters
2023-12-11 12:38 Julian Waters
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=87il5idwr3.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=10walls@gmail.com \
--cc=fweimer@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=nathan@acm.org \
--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).