Last active
August 29, 2015 14:01
-
-
Save mn4367/57bbed35f643a9a0f40f to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| <!DOCTYPE html> | |
| <html lang="en"> | |
| <head> | |
| <meta charset="UTF-8" /> | |
| <title>Hyphenation test</title> | |
| </head> | |
| <body style="width: 10cm;"> | |
| <p lang="en"> | |
| xClang is in­ten­ded spe­cific­ally to work on top of LLVM. | |
| The com­bin­a­tion of Clang and LLVM provides the ma­jor­ity | |
| of a tool­chain, al­low­ing the re­place­ment of the whole | |
| GCC stack. Be­cause it is built with a lib­rary-based design, like the | |
| rest of LLVM, Clang is easy to em­bed in­to oth­er ap­plic­a­tions. | |
| This is one reas­on why a ma­jor­ity of the Open­CL | |
| im­ple­ment­a­tions are built with Clang and LLVM. One of | |
| Clang's primary goals is to bet­ter sup­port in­cre­ment­al | |
| com­pil­a­tion to al­low the com­piler to be more tightly tied | |
| to the IDE GUI. GCC is de­signed to work in a "clas­sic" | |
| com­pile-link-de­bug cycle, and al­though it provides use­ful | |
| ways to sup­port in­cre­ment­al and in­ter­rup­ted | |
| com­pil­ing on-the-fly, in­teg­rat­ing them with oth­er | |
| tools is not al­ways easy. For in­stance, GCC uses a step called "fold" | |
| that is key to the over­all com­pile pro­cess, which has the side ef­fect | |
| of trans­lat­ing the code tree in­to a form that does not look very | |
| much like the ori­gin­al source code. If an er­ror is found dur­ing | |
| or after the fold step, it can be dif­fi­cult to trans­late that back | |
| in­to a single loc­a­tion in the ori­gin­al source. | |
| Ad­di­tion­ally, vendors us­ing the GCC stack with­in IDEs | |
| used sep­ar­ate tools to in­dex the code to provide fea­tures l | |
| ike syn­tax high­light­ing and auto­com­plete. | |
| Clang is de­signed to re­tain more in­form­a­tion | |
| dur­ing the com­pil­a­tion pro­cess than GCC, and | |
| pre­serve the over­all form of the ori­gin­al code. The | |
| ob­ject­ive of this is to make it easi­er to map er­rors back | |
| in­to the ori­gin­al source. The er­ror re­ports offered | |
| by Clang are also aimed to be more de­tailed and spe­cif­ic, as | |
| well as ma­chine-read­able, so IDEs can in­dex the out­put of | |
| the com­piler dur­ing com­pil­a­tion. Mod­u­lar | |
| design of the com­piler can of­fer source code in­dex­ing, | |
| syn­tax check­ing, and oth­er fea­tures nor­mally | |
| as­so­ci­ated with rap­id ap­plic­a­tion | |
| de­vel­op­ment sys­tems. The parse tree is also more | |
| suit­able for sup­port­ing auto­mated code | |
| re­fact­or­ing, as it re­mains in a pars­able text form | |
| at all times. Changes to the pro­gram can be checked by diff­ing the | |
| in­ter­me­di­ate form (IF). | |
| </p> | |
| </body> | |
| </html> |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment