public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/104167] Implement C++20 std::chrono::utc_clock, std::chrono::tzdb etc.
Date: Fri, 01 Sep 2023 11:16:54 +0000 [thread overview]
Message-ID: <bug-104167-4-6L0VV2tes2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104167-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104167
--- Comment #13 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>:
https://gcc.gnu.org/g:f2eb6132c6951edf7960a82828c571a1b98a1a09
commit r14-3616-gf2eb6132c6951edf7960a82828c571a1b98a1a09
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Thu Aug 31 18:31:32 2023 +0100
libstdc++: Avoid useless dependency on read_symlink from tzdb
chrono::tzdb::current_zone uses filesystem::read_symlink, which creates
a dependency on the fs_ops.o object in libstdc++.a, which then creates
dependencies on several OS functions if --gc-sections isn't used. For
more details see PR libstdc++/104167 comment 8 and comment 11.
In the cases where that causes linker failures, we probably don't have
readlink anyway, so the filesystem::read_symlink call will always fail.
Repeat the preprocessor conditions for filesystem::read_symlink in the
body of chrono::tzdb::current_zone so that we don't create a
dependency on fs_ops.o for a function that will always fail.
libstdc++-v3/ChangeLog:
* src/c++20/tzdb.cc (tzdb::current_zone): Check configure macros
for POSIX readlink before using filesystem::read_symlink.
next prev parent reply other threads:[~2023-09-01 11:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 16:16 [Bug libstdc++/104167] New: " redi at gcc dot gnu.org
2022-04-28 9:47 ` [Bug libstdc++/104167] " redi at gcc dot gnu.org
2022-11-13 3:01 ` redi at gcc dot gnu.org
2022-11-13 22:24 ` redi at gcc dot gnu.org
2022-12-22 23:44 ` redi at gcc dot gnu.org
2023-04-26 6:55 ` rguenth at gcc dot gnu.org
2023-07-10 14:43 ` redi at gcc dot gnu.org
2023-07-27 9:22 ` rguenth at gcc dot gnu.org
2023-07-28 19:00 ` redi at gcc dot gnu.org
2023-08-11 18:58 ` cvs-commit at gcc dot gnu.org
2023-08-11 19:00 ` redi at gcc dot gnu.org
2023-08-28 12:49 ` clyon at gcc dot gnu.org
2023-08-28 13:46 ` redi at gcc dot gnu.org
2023-08-28 13:49 ` clyon at gcc dot gnu.org
2023-08-29 19:55 ` redi at gcc dot gnu.org
2023-08-30 13:54 ` clyon at gcc dot gnu.org
2023-09-01 11:16 ` cvs-commit at gcc dot gnu.org [this message]
2023-09-08 17:13 ` cvs-commit at gcc dot gnu.org
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-104167-4-6L0VV2tes2@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).