Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
certik
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
1.
▲
by
certik
2mo ago
Great work, I am glad LFortran worked well for this work. We are very close to beta quality now, many codes just work, pretty much all Fortran features are implemented now, but some codes still don't compile due to various small bugs,
2.
▲
by
certik
2mo ago
We can internally do both row-major and column-major arrays. For Fortran we enable the column-major flag by default, but the door is open to have both at the same time.
3.
▲
by
certik
3mo ago
Just wanted to say big thanks to the maintainers, I've been using tectonic the last couple years as my only LaTeX distribution, works everywhere (including macOS), it's available in conda-forge, so I can just have it as a dependen
4.
▲
by
certik
7mo ago
I do come from the scientific community, so didn't know until today that not every community uses the term "codes".
5.
▲
by
certik
7mo ago
I haven't used vcpkg, but looking at their tutorial at https://learn.microsoft.com/en-us/vcpkg/get_started/get-star... , it seems you still have to use cmake, and if so, it is indeed more complex than fpm
6.
▲
by
certik
7mo ago
No, you "only" have to write a backend. Which is still a lot of work, but much less work than another compiler. There are multiple ways it can be designed, but one idea that I like the most right now is to create an API for LLVM,
7.
▲
by
certik
7mo ago
Yes, that's one answer. But I actually think you can absolutely have both in the same compiler. But you need to have two backends, as I described. You use the custom backend for development (fast to compile) and you use LLVM for releas
8.
▲
by
certik
7mo ago
Author of LFortran here. LFortran is written in C++, because I knew I will be able to fully deliver the project in it. So I know C++ and Fortran very well. I can say for sure that C++ is not superior in every way. It's slower to compil
9.
▲
by
certik
7mo ago
Author of the blog post. It's just being a non-native speaker and writing the blog post by hand shows these little mistakes. I've been using the terms "code" and "codes", but you might very well be right that m
10.
▲
by
certik
7mo ago
Author of LFortran here. The historical answer is that both LFortran and Flang started the same year, possibly the very same month (November 2017), and for a while we didn't know about each other. After that both teams looked at the ot
11.
▲
by
certik
2y ago
It was a lot of corner cases that we had to get right, it's the most advanced code that LFortran can compile. I think none of the features individually is difficult to support, but there were a lot of them.
12.
▲
by
certik
2y ago
Does anyone know how many transistors were on each chip? The complete system of 28 chips had 74,442 transistors. From that it follows that some chip had at least 74,442 / 28 = 2,659 transistors. But I am guessing some chips had less, a
13.
▲
by
certik
2y ago
Beautiful! I would like to see more cursive handwriting fonts. Here is my contribution from 2 years ago: https://certik.github.io/slabikar-otf/
14.
▲
by
certik
2y ago
We are progressing. We'll tackle parallel loops very soon, and get some GPU offloading working. Our main focus is still on just compiling Fortran codes via LLVM. Once we can compile most codes, we'll focus on the various other bac
15.
▲
by
certik
2y ago
The LLVM backend just does the usual floating point calculation for those.
16.
▲
by
certik
2y ago
Yes, I also like The Theoretical Minimum. Ha, I didn't realize there is more than one book! I think I only have the classical mechanics book. Need to buy the other ones. I tried to organize many physics subjects in a similar manner, wi
17.
▲
by
certik
2y ago
Thank you!
18.
▲
by
certik
2y ago
Thanks. Please report all bugs that you find. I talked to my collaborators, we'll try to get some simple demo of Fortran->LLVM->WASM working soon, we need to figure out the runtime library issue (like you did), hook it into the d
19.
▲
by
certik
2y ago
Nothing, we can compile x*3. We can't compile x**3, because we do not have a runtime library setup for WASM yet (Flang above had the same issue) and WASM can do x**2, but arbitrary power, such as x**3, requires a runtime power function
20.
▲
by
certik
2y ago
The author of LFortran here. The demo at https://dev.lfortran.org uses our direct WASM backend that does not use LLVM. It is currently more limited, and indeed, we currently do not support the cubic power x**3 there, only square
21.
▲
by
certik
3y ago
GFortran, Flang and LFortran are all open-source compilers that support modern Fortran.
22.
▲
by
certik
3y ago
Awesome! Report all bugs. :)
23.
▲
by
certik
3y ago
LFortran error messages style got inspired by Rust, and the Fortran Package Manager got inspired by Cargo. And in return Rust can get inspired by LFortran to do the interactive prompt. :) In all seriousness though, Rust got many things righ
24.
▲
by
certik
3y ago
Yes indeed, we'll do it next (unless somebody beats me to it). First I am focusing on compiling fastGPT with LFortran, we can do it, but have a few workarounds that I want to fix. Then we'll do llama2.
25.
▲
by
certik
3y ago
It can be both. If you know the dimension at compile time, it is compile time, if you don't it will be runtime.
26.
▲
by
certik
3y ago
Yes, there are many nice people there and we are doing what we can to moderate the Discourse so that we can all have a nice place to discuss.
27.
▲
by
certik
3y ago
Peter, I am sorry that some users drove you away, possibly myself included. I am personally doing what I can to keep the Fortran open source (and commercial) community together, I have done this before (e.g., with SymPy), and the Fortran co
28.
▲
by
certik
3y ago
LFortran can translate your Fortran code to Julia via our Julia backend. Once Julia can compile to a binary, it will be exciting to do some comparisons, like speed of compilation and performance of the generated binary. As well as the quali
29.
▲
by
certik
3y ago
Yes, both LPython and LFortran are our two thin frontends to ASR (Abstract Semantic Representation). Not just the website is reused, but the internals are reused, so LPython runs your code at exactly the same speed as LFortran would, since
30.
▲
by
certik
3y ago
It's hard to have a fair comparison, and both compilers are also moving targets. I tried to do some comparison in a sibling comment: https://news.ycombinator.com/item?id=37300279 The best is to mention both (as well
More ›