| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| |\ |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The recent change to the way NVCC compilation is handled broke support
for NVRTC. NVRTC can only compile device code, so the host-compilation
approach now used for NVCC (using --keep) is incompatible.
This PR gives the NVRTC compiler its own class and restores the old
behavior. The class is a copy of the old NvccCompiler class, with minor
updates to match the code in the new NvccCompiler class where possible
(plus TypeScript).
This PR also removes NVRTC from `cuda.gpu.properties` (because its
output cannot be executed), and updates the list of versions to match
NVCC.
cc @jrhemstad @trxcllnt
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The recent change to the way NVCC compilation is handled broke support
for NVRTC. NVRTC can only compile device code, so the host-compilation
approach now used for NVCC (using --keep) is incompatible.
This PR gives the NVRTC compiler its own class and restores the old
behavior. The class is a copy of the old NvccCompiler class, with minor
updates to match the code in the new NvccCompiler class where possible
(plus TypeScript).
This PR also removes NVRTC from `cuda.gpu.properties` (because its
output cannot be executed), and updates the list of versions to match
NVCC.
cc @jrhemstad @trxcllnt
|
| |/ |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Makes the Compiler Explorer app, and all the tooling ESM compatible.
Things that have been done:
1. The package.json has `type: module` now
2. All relative imports have a .js ending
3. All directory imports are now directory/index.js to comply with ESM
standards
4. Dependency node-graceful is now imported into tree, because the
package is broken under esm
5. Dependency p-queue has been bumped to 7.x with ESM support
6. Dependency profanities has been bumped to 3.x with ESM support
7. Webpack config is now both ESM and CommonJS compatible
8. Non-ESM compatible imports have been rewritten
9. ESLint configuration has been tweaked to not fail on .js imports
10. Mocha is now hacked together and ran with ts-node-esm
11. Webpack is now hacked together and ran with ts-node-esm
12. Webpack config is now ESM compatible, so that it can be used in the
dev server
13. Cypress code still runs commonjs, and has been excluded from the
tsconfig
14. All sinon mock tests have been commented out, because sinon module
mocks do not work with ESModules (because ESModules are immutable)
A lot of tests are now giving warnings/errors to stdout, yet still pass.
Docenizer codegenerator scripts have been updated, but I did not re-run
them, and instead just changed their code.
---------
Co-authored-by: Matt Godbolt <matt@godbolt.org>
|
| |
|
|
|
| |
Make trailing commas more consistent throughout the project, fixes
config conflict between eslint and prettier. Resolves an oversight in
#4766.
|
| |
|
|
|
|
| |
This PR turns comma-dangle and indent eslint rules on for lib/. These
are rules inherited from the eslint config for static/, this PR just
makes things more consistent. Also turned
@typescript-eslint/no-var-requires back on while I was here.
|
| |
|
|
|
|
|
|
|
|
| |
With the upcoming gcc 13 release and its shiny Modula-2 frontend, we
are introducing Modula-2 support in Compiler Explorer :)
Currently, only the gcc-snapshot build supports modula-2.
fixes #4688
Signed-off-by: Marc Poulhiès <dkm@kataplop.net>
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The compile to binary object has been enabled by mistake for dmd and
ldc, so taking the opportunity to implement it.
ldc is sensitive to output filename extension (.s will force assembly
output, .o binary).
dmd accepts -c to skip the link step.
fixes #4649
Signed-off-by: Marc Poulhiès <dkm@kataplop.net>
|
| |
|
|
|
|
| |
https://github.com/compiler-explorer/compiler-explorer/pull/4674 wasn't
quite finished.
This goes the last mile, and shows the user the options from the
compiler-wrapper.
|
| |
|
| |
If I understand this right this should populate the list of options for the "compiler options" drop-down
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently only list GCC compilers as a first step.
Will add clang in a followup change.
Port gcc.js to Typescript (simple renaming).
Package the objectivec language support for Monaco.
Add very basic example. Something more objc/objc++ specific would be better.
fixes #2942
Signed-off-by: Marc Poulhiès <dkm@kataplop.net>
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
| |
dotnet 6 and 7 will also show the version once there is a new deployment. for now they are showing 7.0.0-dev and <unknown version> respectively
|
| |
|
|
|
|
|
|
|
| |
- latest sentry, tar-stream, which, some yamljs versions
- latest eslint-* stuff
- latest webpack manifest
- Applies all the automatic fixes for newer lint rules
- Bump the webpack version
applies new tslint stuff
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
* Added llvm demangler code
* Added clang-cl compiler class
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Add assert and unwrap utilities
* Playing around with diagnostics
* lib/assert diagnostic implementation
* Remove temporary testing stuff
* Reset package-lock.json to before I messed with it
* Further refinements and integration
* Added licence and removed an obsolete eslint directive
|
| |
|
|
|
|
|
|
|
|
|
|
| |
* Don't try and hack the compilation results
Carbon tried to synthesize "having run" by overriding and hacking a result routine...but did so _after_ it had been cached. So cached results were broken, but live results not.
This "fixes" by adding a post-compilation, but pre-cache hook and uses that instead. Naming is terrible.
I also took the time to fix the `CompilationResult`'s `buildResult`
Closes #4426
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
* Port fortran.js to typescript
* @jeremy-rifkin suggestions
|
| | |
|
| | |
|
