public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mimomorin at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/102259] ifstream::read(…, count) fails when count >= 2^31 on darwin Date: Fri, 10 Sep 2021 09:05:34 +0000 [thread overview] Message-ID: <bug-102259-4-4leGUItH4K@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102259-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102259 --- Comment #2 from Michel Morin <mimomorin at gmail dot com> --- Whoa, darwin's (and FreeBSD's too?) `read(…, …, nbyte)` fails when nbyte >= 2^31! This is the culprit, I think. I also found the following description in FreeBSD's manpage of read (https://www.unix.com/man-page/FreeBSD/2/read/): ERRORS [EINVAL] The value nbytes is greater than INT_MAX. Given that the testcase works file when compiled with Clang, libcxx would have some workround for it.
next prev parent reply other threads:[~2021-09-10 9:05 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-09 14:39 [Bug libstdc++/102259] New: " mimomorin at gmail dot com 2021-09-09 20:22 ` [Bug libstdc++/102259] " redi at gcc dot gnu.org 2021-09-10 9:05 ` mimomorin at gmail dot com [this message] 2021-09-10 20:31 ` pinskia at gcc dot gnu.org 2021-09-11 3:27 ` mimomorin at gmail dot com 2021-09-11 3:32 ` mimomorin at gmail dot com 2021-09-13 9:14 ` redi 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-102259-4-4leGUItH4K@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).