Being Friendly to Your Hardware Performance Engineering A gentle introduction to hardware for software engineers 2Where does C++ run? 3On an abstract C++ machine 4On an abstract C++ machine? specialty instructions, on-core and off- core accelerators • Data layout: both software and hardware characteristics 84 src dst • Alignment: source and destination • Size • Direction • LinearityExample

Instruction Pointers for functions in modules view. Breakpoint Groups Visit https://aka.ms/BreakpointGroups for more details Dependent Breakpoint GroupsIn Visual Studio 2022 version 17.5, CMake Debugger Explorer for Linux Learn more at https://aka.ms/vslinuxEmbedded • On Chip Debugging with hardware breakpoint limits • Peripheral and RTOS object views • Serial monitor • Available in Visual Studio 2022

#define ASSERT(expr) if (!expr) throw AssertFail(); #else // log & terminate, log & continue, breakpoint, assume, ignore... #endif Copyright (c) Timur Doumler | @timur_audio | https://timur #define ASSERT(expr) if (!expr) throw AssertFail(); #else // log & terminate, log & continue, breakpoint, assume, ignore... #endif #define REQUIRE_ASSERT_FAIL(expr) REQUIRE_THROWS(expr, AssertFail) #define ASSERT(expr) if (!expr) throw AssertFail(); #else // log & terminate, log & continue, breakpoint, assume, ignore... #endif #define REQUIRE_ASSERT_FAIL(expr) REQUIRE_THROWS(expr, AssertFail)

main() { std::breakpoint_if_debugging(); //stop if in debugger } 1 2 3 4 5 6 12 support details and Functions Description breakpoint pauses the running program breakpoint_if_debugging calls breakpoint if std::is_debugger_present returns true is_debugger_present checks whether a program is running under the control of a debugger P2546 Debugging Support P2810 is_debugger_present is_replaceable

*** error for object 0x600003488000: pointer being freed was not allocated malloc: *** set a breakpoint in malloc_error_break to debugWidget widget; struct Widget { std::string name = "widget"; dtor: #-1386594240 malloc: *** error for object 0x6000009c4040: pointer being fre malloc: *** set a breakpoint in malloc_error_break to debugWidget widget; struct Widget { std::string name = "widget"; #1157382192 malloc: *** error for object 0x6000037b4030: pointer being freed was not al malloc: *** set a breakpoint in malloc_error_break to debugWidget widget; std::cout << widget.name << "\n"; std::cout << widget

Time auto t) { return d / t; } avg_speed(220 * bu::si::kilo * bu::si::meters, 2 * hours); Breakpoint 2, avg_speedBreakpoint 2, avg_speed, units::unit, units::base_unit< Velocity auto avg_speed(Length auto d, Time auto t) { return d / t; } avg_speed(220_q_km, 2_q_h); Breakpoint 2, avg_speed

the compressor/main.c source file, we can introduce a breakpoint in some line there: Listing 57: main.c int main(void) { ... // add a breakpoint in deflateInit line in your IDE deflateInit(&defstream open our project in Visual Studio and debug it as explained in the previous example. Setting a breakpoint in line 22, running the debugger and using the step into will allow us to debug inside our dependency solution in Visual Studio, we can try to debug again. If you try to step into the dependency, with the breakpoint on line 22, you will notice it will directly skip over to the next line as Visual Studio doesn’t

the compressor/main.c source file, we can introduce a breakpoint in some line there: Listing 61: main.c int main(void) { ... // add a breakpoint in deflateInit line in your IDE deflateInit(&defstream open our project in Visual Studio and debug it as explained in the previous example. Setting a breakpoint in line 22, running the debugger and using the step into will allow us to debug inside our dependency solution in Visual Studio, we can try to debug again. If you try to step into the dependency, with the breakpoint on line 22, you will notice it will directly skip over to the next line as Visual Studio doesn’t

the compressor/main.c source file, we can introduce a breakpoint in some line there: Listing 61: main.c int main(void) { ... // add a breakpoint in deflateInit line in your IDE deflateInit(&defstream open our project in Visual Studio and debug it as explained in the previous example. Setting a breakpoint in line 22, running the debugger and using the step into will allow us to debug inside our dependency solution in Visual Studio, we can try to debug again. If you try to step into the dependency, with the breakpoint on line 22, you will notice it will directly skip over to the next line as Visual Studio doesn’t

section of code to examine • Place an assertion, or set a breakpoint, halfway through the section • If the assertion fires, or the breakpoint is reached with an invalid program state, then the problem