News for hackers. Stuff that matters.
Re:The C23 edition of Modern C is now available for free by renox on Tuesday October 15, 2024 @03:11PM (#41852048)
You'd be surprised: Zig has one UB (Undefined Behaviour) that C doesn't have!

In release fast mode, unsigned overflow/underflow is undefined in Zig whereas in C it wraps.

:-)

Of course C has many UBs that Zig doesn't have, so C is far less safe than Zig, especially since you can use ReleaseSafe in Zig..

Re:The C23 edition of Modern C is now available for free by uecker on Tuesday October 15, 2024 @03:43PM (#41852363)
UB is does not automatically make things unsafe. You can have a compiler that implements safe defaults for most UB, and then it is not unsafe.
Re:The C23 edition of Modern C is now available for free by ahoka on Tuesday October 15, 2024 @04:03PM (#41852548)
By definition UB cannot be safe.
Re:The C23 edition of Modern C is now available for free by marssaxman on Tuesday October 15, 2024 @05:11PM (#41853174)
this depends on your choice of definition for "safe"
Re:The C23 edition of Modern C is now available for free by Maxatar on Tuesday October 15, 2024 @09:58PM (#41854910)
The definition given by the C standard allows for safe undefined behavior.
Re:The C23 edition of Modern C is now available for free by umanwizard on Wednesday October 16, 2024 @09:21AM (#41858758)
Something can be UB according to the standard, but defined (and safe) according to a particular implementation. Lots of stuff is UB according to the C or C++ standard but does something sensible in gcc and/or clang.
Re:The C23 edition of Modern C is now available for free by duped on Tuesday October 15, 2024 @04:54PM (#41853004)
That's implementation defined behavior, not undefined behavior. Undefined behavior explicitly refers to something the compiler does not provide a definition for, including "safe defaults."
Re:The C23 edition of Modern C is now available for free by fuhsnn on Tuesday October 15, 2024 @05:11PM (#41853169)
Compilers are not prohibited to provide their own definition for UB, that's how UBsan exists.
Re:The C23 edition of Modern C is now available for free by Maxatar on Tuesday October 15, 2024 @08:52PM (#41854616)
The C standard says, and I quote:

>Possible undefined behavior ranges from ignoring the situation completely with unpredictable results ... or program execution in a documented manner characteristic of the environment (with or without the issuance of a diagnostic message)

So a compiler is absolutely welcome to make undefined behavior safe. In fact every compiler I know of, such as GCC, clang, MSVC has flags to make various undefined behavior safe, such as signed integer overflow, type punning, casting function pointers to void pointers.

The Linux kernel is notorious for leveraging undefined behavior in C for which GCC guarantees specific and well defined behavior.

It looks like there is also the notion of unspecified behavior, which gives compilers a choice about the behavior and does not require compilers to document that choice or even choose consistently.

And finally there is what you bring up, which is implementation defined behavior which is defined as a subset of unspecified behavior in which compilers must document the choice.

Re:The C23 edition of Modern C is now available for free by renox on Tuesday October 15, 2024 @06:24PM (#41853762)
Well Zig has ReleaseSafe for this.. ReleaseFast is for using these UBs to generate the fastest code.
Re:The C23 edition of Modern C is now available for free by secondcoming on Tuesday October 15, 2024 @04:11PM (#41852615)
Does C automatically wrap? I thought you need to pass `-fwrapv` to the compiler to ensure that.
Re:The C23 edition of Modern C is now available for free by greyw on Tuesday October 15, 2024 @04:36PM (#41852833)
Unsigned overflow wraps. Signed overflow is undefined behavior.
Re:The C23 edition of Modern C is now available for free by kbolino on Tuesday October 15, 2024 @04:45PM (#41852909)
This distinction does not exist in K&R 2/e which documents ANSI C aka C89, but maybe it was added in a later version of the language (or didn't make it into the book)? According to K&R, all overflow is undefined.
Re:The C23 edition of Modern C is now available for free by wahern on Tuesday October 15, 2024 @05:21PM (#41853245)
I don't have my copy of K&R handy, but this distinction has existed since the initial codification. From C89:

  3.1.2.5 Types

  [...] A computation involving unsigned operands can never overflow, because a result that cannot be represented by the resulting unsigned integer type is reduced modulo the number that is one greater than the largest value that can be represented by the resulting unsigned integer type.
Source: C89 (draft) at https://port70.net/~nsz/c/c89/c89-draft.txt
Re:The C23 edition of Modern C is now available for free by renox on Tuesday October 15, 2024 @04:38PM (#41852848)
-fwrapv is for signed integer overflow not unsigned.
Re:The C23 edition of Modern C is now available for free by sp1rit on Tuesday October 15, 2024 @05:02PM (#41853085)
Yes, as unsigned overflow is fine by default. AFAIK the issue was originally that there were still machines that used ones complement for describing negative integers instead of the now customary twos complement.