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: Thu, 28 Apr 2016 19:48:23 +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 #5 from Michael Tautschnig <mt at debian dot org> ---
So that's good for GCC, and really it's making explicit what
"implementation-defined" means for the case of GCC.
The one question that remains open to me is: WHY do we cast back and forth,
when using a signed (long) int would seemingly spare us any debate about
implementation-definedness?
Thanks a lot,
Michael
--
You are receiving this mail because:
You are on the CC list for the bug.