search for: my_new_arch

...nd subset, and throwing "Not Supported" exceptions where ever appropriate. To give a concrete example, take a simple CPU architecture that does not support floating point arithmetic, but does support simple integer arithmetic. If my LLVM frontend produces only i32 values, then `llc -march=my_new_arch` doesn't complain. If, however, my frontend produces float values, then `llc -marc=my_new_arch` would complain with the "Type 'float' Not Supported by architecture my_new_arch". Is this the philosophy of LLVM backend implementation? Must the new target architecture support al...

...ing "Not Supported" exceptions where ever > appropriate. To give a concrete example, take a simple CPU > architecture that does not support floating point arithmetic, but does > support simple integer arithmetic. If my LLVM frontend produces only > i32 values, then `llc -march=my_new_arch` doesn't complain. If, > however, my frontend produces float values, then `llc > -marc=my_new_arch` would complain with the "Type 'float' Not Supported > by architecture my_new_arch". > > Is this the philosophy of LLVM backend implementation? Must the new > t...