public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "nicolas at debian dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ada/114065] gnat build with -D_TIME_BITS=64 -D_FILE_OFFSET_BITS=64 fails on 32bit archs Date: Mon, 20 May 2024 17:44:55 +0000 [thread overview] Message-ID: <bug-114065-4-mBDqUezqKG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114065-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114065 Nicolas Boulenguez <nicolas at debian dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #58060|0 |1 is obsolete| | Attachment #58181|0 |1 is obsolete| | --- Comment #27 from Nicolas Boulenguez <nicolas at debian dot org> --- Created attachment 58252 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58252&action=edit Version 10, tarball with 8 commits + tests Hello. Version 10 * restores support for time_t in System.OS_Lib, with a comment saying that the type is now unrelated with C (patch 4/8). * restores support for timespec in Ada.Calendar.Conversions and timeval in GNAT.Calendar, via wrappers delegating to C_Time. The subtype ranges for the parameters are tighter, but that only makes preexisting pre- and post-conditions explicit. * unsuppresses the Overflow_Check * replaces pre- and post-conditions with subtype ranges * fixes a type name in docs (patch 3/8) * fixes a typo on android * roughly sorts the patches by decreasing importance (only 1-2 fix bugs) The restorations hopefully answer the concerns expressed by Arnaud Charlet at https://gcc.gnu.org/pipermail/gcc-patches/2024-May/651794.html. In Ada.Calendar, the changes only affect the private part.
prev parent reply other threads:[~2024-05-20 17:44 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-22 19:40 [Bug ada/114065] New: " doko at gcc dot gnu.org 2024-02-26 11:04 ` [Bug ada/114065] " ebotcazou at gcc dot gnu.org 2024-03-22 0:05 ` pinskia at gcc dot gnu.org 2024-03-22 0:57 ` doko at gcc dot gnu.org 2024-03-22 8:05 ` ebotcazou at gcc dot gnu.org 2024-03-23 18:55 ` ebotcazou at gcc dot gnu.org 2024-04-03 17:46 ` nicolas at debian dot org 2024-04-03 17:47 ` nicolas at debian dot org 2024-04-03 17:48 ` nicolas at debian dot org 2024-04-03 17:48 ` nicolas at debian dot org 2024-04-03 17:49 ` nicolas at debian dot org 2024-04-03 17:49 ` nicolas at debian dot org 2024-04-04 10:12 ` charlet at gcc dot gnu.org 2024-04-04 14:20 ` nicolas at debian dot org 2024-04-04 14:45 ` nicolas at debian dot org 2024-04-05 16:30 ` nicolas at debian dot org 2024-04-05 16:36 ` nicolas at debian dot org 2024-04-06 11:37 ` ebotcazou at gcc dot gnu.org 2024-04-08 9:19 ` nicolas at debian dot org 2024-04-11 10:53 ` nicolas at debian dot org 2024-04-24 10:26 ` doko at gcc dot gnu.org 2024-04-24 10:33 ` doko at gcc dot gnu.org 2024-04-24 17:19 ` nicolas at debian dot org 2024-04-24 22:47 ` nicolas at debian dot org 2024-04-28 20:32 ` nicolas at debian dot org 2024-05-02 15:34 ` nicolas at debian dot org 2024-05-11 8:46 ` nicolas at debian dot org 2024-05-20 17:44 ` nicolas at debian dot org [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-114065-4-mBDqUezqKG@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).