aboutsummaryrefslogtreecommitdiff
path: root/FAQ.md
Commit message (Collapse)AuthorAgeFilesLines
* Update broken link in FAQ.md (#1488)Derek Schuff2023-10-231-1/+1
| | | Fixes #1487
* FAQ: Fix Assorted Typos (#1461)Conner2022-09-291-9/+9
| | | | | - Clarify language when talking about LLVM - Correct "but which can..." to "but can..." - "...this issue at point" to "this issue at some point"
* Fix broken links (#1326)Tom Klaver2020-02-181-1/+1
| | | Existing link (https://jsmodules.io) is broken. Can be replaced with this MDN link?
* Fix broken links to GC.md (#1209)Kenrick2020-01-131-1/+1
| | | | | | * Fix broken links to GC.md * Update links to proposals repo
* rewrite URLs (http:// -> https://) (#1205)Romario Maxwell2018-05-041-4/+4
| | | | | | All the modified URLs were checked to see if they are available over HTTPS by opening a new tab in the browser, entering the URL in the address bar, changing http:// to https:// and then verifying if the resource displayed is the same over HTTP and HTTPS for each URL.
* Fixup links to future features (#1157)Joseph Richey2017-11-151-5/+5
| | | | | | | | | | | | | | | | | | This link standardizes how all the other design pages will refer to future features (either in `FutureFeatures.md` or in a tracking issue). All links to these upcoming features now use references at the bottom of the doc page (as opposed to inline links or references). Note that this change makes it very easy for the doc links to be updated when a tracking issue is started. As all the references have a standard format; a simple find/replace script will get everything. This commit also makes sure that references now point to a tracking issue if one exists. Note that this means a future CL can now delete some of the unnecessary sections from `FutureFeatures.md`. The only visible change from this commit is that certain broken links are now fixed, or links pointing to a doc section now point to the correct tracking issue.
* Tagging future features with icon. (#839)Brad Nelson2016-10-271-8/+14
| | | Added brief item on multiple return.
* Structured stack (#813)titzer2016-10-111-1/+1
| | | | | | | | | | | | | | | | | | | | * Rename AstSemantics.md to Semantics.md * Rewrite Semantics for structured stack machine * Update control instructions * Update nop * More tweaks * Update README.md * Update Semantics.md * Update Semantics.md * Address @rossberg-chromium comments
* polyfilling update (#737)Alon Zakai2016-08-031-38/+28
|
* Fix grammatical error (#718)Randy Westlund2016-06-301-1/+1
|
* fix grammar (#679)Joshua Olson2016-05-011-1/+1
|
* Access to proprietary APIs apart from HTML5 (#656)Alexander Orlov2016-04-151-0/+9
|
* Remove extraneous parenthesisBrett Cannon2015-11-021-1/+1
|
* Replace `operation` with `operator`titzer2015-10-231-5/+5
|
* ChromimumLuke Wagner2015-10-231-1/+1
|
* Update various references to "builtin" operations.Dan Gohman2015-10-121-2/+3
|
* Update FAQJF Bastien2015-10-091-139/+227
| | | | I was going to move some of it to rationale.md, but I figure I should format things similarly, and update some of what's now outdated first.
* Only allow memory growth in MVPLuke Wagner2015-10-061-3/+3
|
* Capitalize Instruction Set Architecture.Dan Gohman2015-09-141-1/+1
|
* Expand the ISA acronym at its first use.Dan Gohman2015-09-141-1/+1
|
* Say ISA instead of IR when describing WebAssembly.Dan Gohman2015-09-141-4/+4
|
* Update FAQ.mdJF Bastien2015-09-141-1/+1
|
* Add an FAQ about using 8 bytes for storing pointers.Dan Gohman2015-09-081-0/+15
|
* Add an FAQ entry explaining the lack of an abstract `size_t`.Dan Gohman2015-09-051-0/+26
|
* Merge pull request #265 from WebAssembly/jit-libraryDan Gohman2015-08-211-1/+1
|\ | | | | Add a page about a JIT/Optimization library idea.
| * Add a new page about the JIT/Optimization library concept.Dan Gohman2015-08-191-1/+1
| | | | | | | | | | This also obviates the need for the floating point library function section.
* | Fix typo.Dan Gohman2015-08-201-1/+1
|/
* Remove the useful anecdotesLuke Wagner2015-08-121-6/+3
|
* Tweak FAQ wordingLuke Wagner2015-08-121-3/+3
|
* Address first round of commentsLuke Wagner2015-08-121-1/+1
|
* Clarify, rename, and FAQ memory allocationLuke Wagner2015-08-121-0/+33
|
* Consolidate explanation of modules into a new Modules.md and improve explanationLuke Wagner2015-07-241-1/+1
|
* Fix typos.Dan Gohman2015-07-231-1/+1
|
* Mention that middle-end optimization can benefit from feature tests.Dan Gohman2015-07-231-0/+2
|
* Add code quotes.Dan Gohman2015-07-171-1/+1
|
* Don't mention feature-testing for FMA here.Dan Gohman2015-07-171-1/+1
|
* Add a FAQ explaining why there is no fast-math mode.Dan Gohman2015-07-171-0/+17
|
* Point to Streams Standard in active developmentMichael[tm] Smith2015-06-221-1/+1
| | | | | | This duplicates #195 from @annevk (which couldn’t be merged since the fork it came from was afterward deleted). Signed-off-by: Michael[tm] Smith <mike@w3.org>
* Update FAQ.mddann toliver2015-06-201-2/+2
| | | Two typo fixes
* Clarify UB as runtime unpredictability and IR as standard formatDerek Schuff2015-06-181-6/+6
|
* Remove last sentence of LLVM description and merge paragraphsDerek Schuff2015-06-181-8/+3
|
* Simplify first sentence about LLVM IRDerek Schuff2015-06-181-9/+9
|
* Grammar!Derek Schuff2015-06-181-1/+1
|
* fix typo in linkDerek Schuff2015-06-181-1/+1
|
* Add mention of UB and wordsmith a bitDerek Schuff2015-06-181-5/+11
|
* reviewDerek Schuff2015-06-181-4/+5
|
* Add "Why not use LLVM IR" to FAQDerek Schuff2015-06-181-0/+43
|
* Why? Mention compression and link to stream APIJF Bastien2015-06-171-1/+2
|
* add some context in 'which compilers' about how the new LLVM backend can be usedAlon Zakai2015-06-161-4/+6
|
* Merge pull request #179 from WebAssembly/drop-llvm-refsLuke Wagner2015-06-161-11/+9
|\ | | | | Drop references to LLVM repo
generated by cgit v1.2.3 (git 2.39.1) at 2026-06-12 06:43:51 +0000