search for: t210

When I worked on the HPE NonStop compilers for x86 (we used Open64, not LLVM), we adjusted our -O1 to make sure the source display didn't "bounce around" based on feedback from users. We disabled any optimization that would move things across statement boundaries. We also disabled/de-tuned dead store since our DWARF location list support was pretty basic and with the removed store,

...ubcommand failed. My hardware is a rather ancient HP a6745f (AMD) with 4GB memory, 200 GB HDD. OS is Kubuntu 18.10. Is my system just too limited or is there something else I should look for? What other info can I provide? Ron -- Ron Brender Whose favorite airplane is N6119A, a 1979 Cessna T210.

Hello Djordje, Vedant, Thanks a lot for sharing information. I have a doubt, please consider the following simple test case- #include <iostream> int func(int* ptr){ std::cout << *ptr; return *ptr + 5; } int main(int argc, char** argv){ int a = 4; int* ptr_a = &a; int b = func(ptr_a); return 0; } commandline used -- bash$ clang++