Gitiles
Code Review Sign In
gerrit-public.fairphone.software / toolchain / llvm-project / 369bddf5ad8cb1543d38d4afd12cce768292114a / llvm / docs / FAQ.html
  1. fc8d930 docs: Use <Hn> as Heading elements instead of <DIV class="doc_foo">. by NAKAMURA Takumi · 15 years ago
  2. ca46f5a docs: Canonicalize URLs. by NAKAMURA Takumi · 15 years ago
  3. d6a6f61 Fix whitespace to be more consistent with AsmPrinter's style. by Dan Gohman · 15 years ago
  4. f375e9a Revert r103213. It broke several sections of live website. by mike-m · 16 years ago[Renamed from llvm/docs/main/FAQ.html]
  5. e08af30 Overhauled llvm/clang docs builds. Closes PR6613. by mike-m · 16 years ago[Renamed from llvm/docs/FAQ.html]
  6. a25ee78 one more thing. by Chris Lattner · 16 years ago
  7. f3d99aa update instructions for llvm-gcc4, the brave new world! PR7037 by Chris Lattner · 16 years ago
  8. f804f18 Fix a typo. by Dan Gohman · 16 years ago
  9. 0f42038 Documentation: Perform automated correction of common typos. by Benjamin Kramer · 16 years ago
  10. c4501d5 add a FAQ. by Chris Lattner · 16 years ago
  11. 5e8b8b3 Fixed spelling. by Misha Brukman · 17 years ago
  12. b01824a Use 'name' instead of 'href'. by Bill Wendling · 17 years ago
  13. ebb4486 Fix verification failure. by Bill Wendling · 17 years ago
  14. bf448a1 Offer an explanation of why building LLVM-GCC with objdir == srcdir doesn't by Bill Wendling · 17 years ago
  15. 1ae487b Another reformatting. No change in docs. by Bill Wendling · 17 years ago
  16. 6b30968 fix broken GCC bugzilla link by Gabor Greif · 17 years ago
  17. 143bf8b add a Q/A on broken GCCs by Gabor Greif · 17 years ago
  18. 1093e9a Answer a common FAQ: by Dan Gohman · 17 years ago
  19. e3f2278 Reality-check the FAQ entry for "Can I use LLVM to convert C++ to C?" by Dan Gohman · 17 years ago
  20. 29f390b Simplified marking code regions -- no need to use <div> to surround <pre> tags. by Misha Brukman · 17 years ago
  21. 6c321b6 Instead of referring to the license file in the 2.3 release, refer to the by Misha Brukman · 17 years ago
  22. 86242e1 Global replace of yellow W3C "valid HTML/CSS" icons with blue ones. by Misha Brukman · 17 years ago
  23. 8ef4498 Fix a few HTML tidiness issues. by Dan Gohman · 17 years ago
  24. dc69391 Stacker is dead. by Duncan Sands · 17 years ago
  25. 94cefef Update LICENSE link. by Daniel Dunbar · 17 years ago
  26. 60c1404 Improving wording. by Gordon Henriksen · 18 years ago
  27. 6ee6b7c Adding a note about IR generation to the LLVM FAQ. by Gordon Henriksen · 18 years ago
  28. da19884 __main is dead along with llvm-gcc3. by Chris Lattner · 18 years ago
  29. beee622 Validation fixes by Bill Wendling · 18 years ago
  30. c7f87f2 Subversionify the documentation. by Reid Spencer · 18 years ago
  31. a54634a first pass of nomenclature changes in .html files by Gabor Greif · 18 years ago
  32. 0a303eb Added "llvmc" to the FAQ. by Bill Wendling · 18 years ago
  33. 2c22fcb Added "doc_class" div tags to code segments. by Bill Wendling · 18 years ago
  34. d521f3c remove an obsolete question by Chris Lattner · 19 years ago
  35. a7974cc Remove references to gccld and gccas, adjusting the documentation to by Reid Spencer · 19 years ago
  36. b096190 Add a note about C++ -> C with libstdc++ by Chris Lattner · 19 years ago
  37. 667c901 Add a link in a prominant location. by Chris Lattner · 19 years ago
  38. 4bded9c Answer the most frequently asked question, about GEPs. The answer is by Reid Spencer · 19 years ago
  39. 7b1d3c0 Answer the FAQ: "can llvm convert C++ code to C?" by Chris Lattner · 19 years ago
  40. 027fbc2 Actually, semantical doesn't appear to be a word. by Jeff Cohen · 20 years ago
  41. 6b764e7 Unfortunately this really isn't the place for advertisement. by Chris Lattner · 20 years ago
  42. e42f3ba Fix typo. by Jeff Cohen · 20 years ago
  43. 4d3171f Fix some anchors. by Reid Spencer · 20 years ago
  44. 9aa244e Add some notes about the current state of source (front end) languages by Reid Spencer · 20 years ago
  45. ca05854 Changes docs for llvm.cs.uiuc.edu -> llvm.org by Reid Spencer · 20 years ago
  46. af0ac27 Added question about turning off all optimizations. I think this has been asked once or twice. by Tanya Lattner · 21 years ago
  47. 37d5547 add an entry, add links to entries for demo page. by Chris Lattner · 21 years ago
  48. 360d6b7 Remove most references to LLVM_LIB_SEARCH_PATH. It now only exists in the by Reid Spencer · 21 years ago
  49. 79e49cf Correct documentation to reflect the change in location of the CFE runtime by Reid Spencer · 21 years ago
  50. ba739a8 We don't have python test classes anymore. by John Criswell · 21 years ago
  51. 8d9a83a * Link to the license file from release 1.3 (should we link to CVS version by Misha Brukman · 21 years ago
  52. 4657235 If updating from CVS gives error "No rule to make target", it's faster to just by Misha Brukman · 21 years ago
  53. 5363e38 * Standardize footer * HTML 4.01 (Strict) compliance by Misha Brukman · 21 years ago
  54. 020e1fc Make use of the new doc_author class. "Seperate content from presentation" they said. by Chris Lattner · 21 years ago
  55. fa2f368 Merged in RELEASE_12. by John Criswell · 22 years ago
  56. 87d6b40 Add a faq entry by Chris Lattner · 22 years ago
  57. d89dbd0 Point to the new license (includes year 2004). Changed crtend.o to libcrtend.a. by John Criswell · 22 years ago
  58. 5695ec9 Corrected typo. by John Criswell · 22 years ago
  59. 5abdc6f The GCC problem is not specific to suse by Chris Lattner · 22 years ago
  60. e7670a0 Add a faq entry for the demo page by Chris Lattner · 22 years ago
  61. d899432 `effect' is the noun, `affect' is the verb. by Misha Brukman · 22 years ago
  62. 408916b Add note about sucky suse compiler by Chris Lattner · 22 years ago
  63. 2335331 add new FAQ entry by Chris Lattner · 22 years ago
  64. 956cf45 Added the new GCC front end section to the table of contents. by John Criswell · 22 years ago
  65. 5e0f07e Added information on the GCC front end. by John Criswell · 22 years ago
  66. 6c91a33 * Added a "contents"-like list of questions at the beginning of the file by Misha Brukman · 22 years ago
  67. 5b4dea3 The answer to this question is "Yes". Let's make that absolutely clear even to by Misha Brukman · 22 years ago
  68. 8a98cd1 Call me picky, but it's not the state of Illinois' license, it's the by Misha Brukman · 22 years ago
  69. 4da8cb0 Rephrase the OSI answer. by Vikram S. Adve · 22 years ago
  70. a227488 Dang...these different file locations make it a pain to get the URLs right. by Vikram S. Adve · 22 years ago
  71. c021b23 Fix license URL and typo. by Vikram S. Adve · 22 years ago
  72. 26c901e Improve formatting of licensing section. by Vikram S. Adve · 22 years ago
  73. 71e433e Add a section on licensing questions. by Vikram S. Adve · 22 years ago
  74. ebe140b Added answers to test suite questions. by John Criswell · 22 years ago
  75. 8af7320 Fequently Asked Questions about LLVM. Mainly focuses on build problems, but by John Criswell · 22 years ago