Hi, It's good that llvm/lib builds with exceptions and RTTI disabled as it supports doing optimization and codegen on very constrained platforms. Judging by REQUIRES_EH in makefiles, only a few bits like TableGen, llvm-ar and llvm-ranlib need them, and I doubt these would need to run on a target. It's unlikely exceptions would get in in a random patch, because it would have to change the makefile; but even so, it would be useful to know that it's due to a definite design rule (assuming that's the case). Maybe this could be added to http://llvm.org/docs/CodingStandards.html ? Al -- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Hi Al,> It's good that llvm/lib builds with exceptions and RTTI disabled as it > supports doing optimization and codegen on very constrained platforms. > Judging by REQUIRES_EH in makefiles, only a few bits like TableGen, llvm-ar > and llvm-ranlib need them, and I doubt these would need to run on a target. > It's unlikely exceptions would get in in a random patch, because it would > have to change the makefile; but even so, it would be useful to know that > it's due to a definite design rule (assuming that's the case). > Maybe this could be added to http://llvm.org/docs/CodingStandards.html ?yes, it's a definite design rule. Can you please send a doc patch for CodingStandards with some appropriate text in it. Thanks a lot, Duncan.
In that case, RTTI and exception should also be disabled from CMake generated projects right? Currently they are enabled all over my MSVC projects. On Thu, Oct 14, 2010 at 3:57 AM, Duncan Sands <baldrick at free.fr> wrote:> Hi Al, > >> It's good that llvm/lib builds with exceptions and RTTI disabled as it >> supports doing optimization and codegen on very constrained platforms. >> Judging by REQUIRES_EH in makefiles, only a few bits like TableGen, llvm-ar >> and llvm-ranlib need them, and I doubt these would need to run on a target. >> It's unlikely exceptions would get in in a random patch, because it would >> have to change the makefile; but even so, it would be useful to know that >> it's due to a definite design rule (assuming that's the case). >> Maybe this could be added to http://llvm.org/docs/CodingStandards.html ? > > yes, it's a definite design rule. Can you please send a doc patch for > CodingStandards with some appropriate text in it. > > Thanks a lot, > > Duncan. > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >
Seemingly Similar Threads
- [LLVMdev] LLVM use of C++ exceptions and RTTI
- [LLVMdev] LLVM use of C++ exceptions and RTTI
- [LLVMdev] LLVM use of C++ exceptions and RTTI
- [LLVMdev] Disabling rtti on default build - could it be reverted/re-enabled?
- [LLVMdev] LLVM use of C++ exceptions and RTTI