News for hackers. Stuff that matters.
Re:C and C++ Prioritize Performance over Correctness by lelanthran on Friday August 18, 2023 @02:21PM (#37179937)
I fail to see to the point of your post in context of this thread.

What, in the parent post, do you consider a myth?

Re:C and C++ Prioritize Performance over Correctness by pjmlp on Friday August 18, 2023 @02:28PM (#37180028)
C's original performance.

Optimization taking advantage of UB had to be introduced during the 1990's to make it into a reality.

Until the widespread of 32 bit hardware, even junior Assembly devs could relatively easy outperform C compilers.

Which is what the interview is about, originally C lacked the optimization tools, relying on developers, with tons of inline Assembly.

Re:C and C++ Prioritize Performance over Correctness by lelanthran on Friday August 18, 2023 @02:44PM (#37180261)
> Which is what the interview is about, originally C lacked the optimization tools, relying on developers, with tons of inline Assembly.

I'm afraid that is not the conclusion I draw from the snippet you posted.

It's very clear to me that the HLL under question at that time prevented the programmer from performing the low-level optimisations that the C programmer could optionally do. The debate appeared to be be whether to let the language exclusively optimise the code, or just do no optimisation and let the programmer do it.

This is why the sentence ": Oh, yeah. That would have been fine. And, in fact, you need to have something like that, something where experts can really fine-tune without big bottlenecks because those are key problems to solve. " is in there - it's because the HLL languages literally wouldn't let the programmer optimise at the level that C would let the programmer optimise.

Honestly, if the proponent for the HLL language didn't add in "Use the HLL, but not for OS and low-level code where you really need to fine-tune", you'd have a point, but they said it, and so you don't.

Re:C and C++ Prioritize Performance over Correctness by pjmlp on Friday August 18, 2023 @04:03PM (#37181337)
Right, that is why C code was polluted with inline Assembly until optimizers started taking advantage of UB.

Inline Assembly isn't C.

Re:C and C++ Prioritize Performance over Correctness by memefrog on Friday August 18, 2023 @08:44PM (#37184168)
Of course inline assembly is C. Most languages don't let you do inline assembly. That isn't because they don't like it, but because the way those languages get translated to machine code is highly variable. C is the only language where the semantic model is simple enough that you can see how every language construct would translate to assembly language and write your own inline assembly language in between.
Re:C and C++ Prioritize Performance over Correctness by pjmlp on Saturday August 19, 2023 @02:59AM (#37186275)
It definitely isn't.

What page of C standard describes it?

As for the rest of your comment, unless you are using a PDP-11, you will be surprised.

Re:C and C++ Prioritize Performance over Correctness by memefrog on Saturday August 19, 2023 @03:21AM (#37186374)
C predates the C standard, which describes a common subset of C implementations. It is useful for writing code which works across a variety of implementations. For example, you can write code that works on the Byzantine optimising compilers, which will attempt to render your code incorrectly if at all possible, but will make strictly conforming programs run very quickly. But it is not necessary to write code to the C standard, and many C implementations do not conform to it. The Plan9 C compiler, for example, expects 'void main(void)' for a program's main function, while the standard requires 'int main(void)'.
Re:C and C++ Prioritize Performance over Correctness by pjmlp on Saturday August 19, 2023 @06:19AM (#37187267)
Lets make it easier then, what page of K&R C describes inline Assembly?
Re:C and C++ Prioritize Performance over Correctness by memefrog on Saturday August 19, 2023 @06:36AM (#37187360)
[delayed]
Re:C and C++ Prioritize Performance over Correctness by pjmlp on Saturday August 19, 2023 @10:04AM (#37188900)
Likewise compiler specific extensions don't define universal truths about languages, that aren't part of the respective standard.

Had you been clever, you would have pointed out that inline Assembly is defined in the ANSI C++ standard, with the mention of asm (content) language construct, leaving the meaning of content implementation defined.

As it is also defined in the Ada language standard, Modula-2 standard revision, and Oakwood Guidelines for Oberon-2 implementation.

That is the thing mixing up C with compiler specific features, confusing the language for its standard and assuming no other language in the planet offers similar capabilities.

Re:C and C++ Prioritize Performance over Correctness by memefrog on Saturday August 19, 2023 @10:16AM (#37189021)
I am not remotely interested in what the ISO standard says about C, and I am even less interested in what the ANSI standard says about C++, a completely different language.

C is not defined by or constrained to the standard. It predates it and every implementation extends it, as is intended by the standard.

The person confusing the standard with the language is you.

Re:C and C++ Prioritize Performance over Correctness by defrost on Saturday August 19, 2023 @06:36AM (#37187361)
The more important detail is which "standard C" recognises inline asm as a common as dirt C extension.

Page 514 (of version n1256) of the ISO C Standard

Moving target, to be, sure, but it's been there for 20+ years now.

Annex J.5.10 The asm keyword

to quote a stack overflow answer (that sounds a lot like an answer commonly given back in the day on Usenet and #C IRC channels)

     informative, not normative, so an implementation need not provide inline assembly, and if it does it's not prescribed in which form. But it's a widespread extension, though not portable since compilers do indeed implement it differently.
https://www.open-std.org/JTC1/SC22/WG14/

https://www.open-std.org/jtc1/sc22/wg14/www/docs/n1256.pdf