public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "eggert at cs dot ucla.edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/114965] [13/14/15 Regression] wrong code generated for Emacs/Gnulib strftime (regression from 13.2) Date: Tue, 07 May 2024 16:38:35 +0000 [thread overview] Message-ID: <bug-114965-4-B8bJVqp4NC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114965-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114965 --- Comment #12 from Paul Eggert <eggert at cs dot ucla.edu> --- Thanks for fixing GCC. I installed into Gnulib a patch that clarifies strftime's implementation, and this also works around the GCC bug. It'll take some time for this to propagate out, though, as Gnulib is a source code library and each package incorporates Gnulib code when it sees fit. The patch is here: https://git.savannah.gnu.org/cgit/gnulib.git/commit/?id=4121ae7ad2859331447fe719d255e3d22953f327
next prev parent reply other threads:[~2024-05-07 16:38 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-06 22:17 [Bug c/114965] New: " eggert at cs dot ucla.edu 2024-05-06 23:05 ` [Bug middle-end/114965] " pinskia at gcc dot gnu.org 2024-05-06 23:07 ` [Bug tree-optimization/114965] [14/15 Regression] " pinskia at gcc dot gnu.org 2024-05-06 23:08 ` pinskia at gcc dot gnu.org 2024-05-06 23:10 ` [Bug tree-optimization/114965] [13/14/15 " pinskia at gcc dot gnu.org 2024-05-06 23:35 ` pinskia at gcc dot gnu.org 2024-05-06 23:45 ` pinskia at gcc dot gnu.org 2024-05-07 4:45 ` sjames at gcc dot gnu.org 2024-05-07 8:51 ` rguenth at gcc dot gnu.org 2024-05-07 9:49 ` sjames at gcc dot gnu.org 2024-05-07 11:25 ` jakub at gcc dot gnu.org 2024-05-07 11:49 ` jakub at gcc dot gnu.org 2024-05-07 16:24 ` jakub at gcc dot gnu.org 2024-05-07 16:38 ` eggert at cs dot ucla.edu [this message] 2024-05-08 8:18 ` cvs-commit at gcc dot gnu.org 2024-05-08 8:19 ` cvs-commit at gcc dot gnu.org 2024-05-08 8:20 ` [Bug tree-optimization/114965] [13 " jakub at gcc dot gnu.org 2024-05-09 4:27 ` cvs-commit at gcc dot gnu.org 2024-05-09 8:19 ` jakub 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-114965-4-B8bJVqp4NC@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: linkBe 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).