public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/94076] libsanitizer fails with 64-bit time_t Date: Mon, 09 Mar 2020 11:27:17 +0000 [thread overview] Message-ID: <bug-94076-4-FgRURXxoBe@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94076-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94076 --- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Well, 64-bit time_t/off_t/ino_t on an arch where they weren't previously 64-bit is an ABI change which of course needs to have support added to various parts of the toolchain, including libsanitizer (for which it should go through the upstream).
next parent reply other threads:[~2020-03-09 11:27 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-94076-4@http.gcc.gnu.org/bugzilla/> 2020-03-09 11:27 ` jakub at gcc dot gnu.org [this message] 2021-07-18 18:16 ` pinskia 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-94076-4-FgRURXxoBe@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).