Timeline for int128 handling in c-code, gcc / glibc / linux
Current License: CC BY-SA 4.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 14 at 4:19 | history | edited | user1018684 | CC BY-SA 4.0 |
Added hint on similar C++ project.
|
| Feb 3 at 13:55 | comment | added | user1018684 | @chux : you seem experienced with the wide types? Two questions: - my system somehow supports 128-bit integers: 'size of INT128: 16', but all '~ll' functions seem restricted to 64-bit, same as the '~l' functions. Can they work for int128? E.g. is it possible to rewrite the example in en.cppreference.com/w/c/string/wide/wcstoul for wcstoull and unint128? If - how, and what versions / environment / options are minimally needed. TIA for any clarification. | |
| Feb 1 at 9:08 | answer | added | user1018684 | timeline score: 1 | |
| Feb 1 at 3:39 | history | became hot network question | |||
| Jan 31 at 22:20 | comment | added | chux |
" I overlooked something? " --> It is a deep issue involving intmax_t and super wide types now supported by C23. It is glacially getting better.
|
|
| Jan 31 at 21:43 | answer | added | chux | timeline score: 10 | |
| Jan 31 at 21:35 | answer | added | toolic | timeline score: 5 | |
| Jan 31 at 21:23 | answer | added | user272752 | timeline score: 7 | |
| Jan 31 at 21:01 | comment | added | user272752 | It's a deep, deep dive for a beginner, but this video might prove interesting to you. Not only "non-portable", but would subtly bind the app to the installed libc on your system (if it works for you). You co-worker's system may happily be functioning with an older libc that doesn't support this... Still, a learning experience... | |
| Jan 31 at 20:28 | answer | added | CPlus | timeline score: 7 | |
| Jan 31 at 19:52 | history | edited | toolic | CC BY-SA 4.0 |
edited tags
|
| Jan 31 at 19:50 | history | migrated | from codereview.meta.stackexchange.com (revisions) | ||
| Jan 31 at 19:33 | history | asked | user1018684 | CC BY-SA 4.0 |