This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/19995] Linux syscall return value unnecessarily relies on implementation-defined behaviour
- From: "mt at debian dot org" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Tue, 26 Apr 2016 14:15:18 +0000
- Subject: [Bug libc/19995] Linux syscall return value unnecessarily relies on implementation-defined behaviour
- Auto-submitted: auto-generated
- References: <bug-19995-131 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=19995
--- Comment #2 from Michael Tautschnig <mt at debian dot org> ---
Unless I'm wrong about what rule is to be applied here, the standard says in
"6.3.1.3 Signed and unsigned integers", paragraph 3:
"Otherwise, the new type is signed and the value cannot be represented in it;
either the result is implementation-defined or an implementation-defined signal
is raised."
But I do accept that this has seemingly been working in practice for a quite a
while (as makes sense, because this is implementation-defined, not undefined,
behaviour).
Best,
Michael
--
You are receiving this mail because:
You are on the CC list for the bug.