> Whilst many alternative programming languages have come and gone, it [Fortran] has regained its popularity for writing high performance codes. I don't understand why sometimes people pluralize "code". It sounds a bit silly but maybe it's just me.
It's because the types of things people write in Fortran (high performance science codes, for example) tend to be monolithic, single-purpose programs. It comes from a time when a code really was basically one compilation unit (and doing that is such a nice simplification that I support it, for science). With code written for the web, shared through package managers, etc. it makes more sense to use the uncountable nou…
First official release of LLVM Flang
11–20 of 28 posts
Re: First official release of LLVM Flang
#12> Whilst many alternative programming languages have come and gone, it [Fortran] has regained its popularity for writing high performance codes. I don't understand why sometimes people pluralize "code". It sounds a bit silly but maybe it's just me.
I'm seeing it here for the first time, and from multiple people. Maybe it's specific to the Fortran community?
So in this sense, as a synonym for a library or a program that accomplishes some function, "code" is countable.
Re: First official release of LLVM Flang
#13How compatible is it with the current code bases developped under proprietary compilers ?
Re: First official release of LLVM Flang
#14Not sure if I would use it today for new projects, probably Julia would be the better choice nowadays.
Re: First official release of LLVM Flang
#15Congratulations to the team, this has been a long time coming. I still think that modern Fortran is actually a great language to write numerical code, especially when doing lots of linear algebra. Granted, it was many years ago, but I still remember struggling with C++ and libraries like Eigen, and one day, confronted yet again with agonizing slow compile times and error messages that look like binary, I ditched C++…
Re: First official release of LLVM Flang
#16Now someone go convince the C committee to stop trying to turn C into Fortran.
Q from out of the loop: what are you referring to? and if you could enlighten me how that then is a problem?
In C99, C added the 'restrict' qualifier for pointers, which would make function arguments marked with it behave a bit like procedure arguments in Fortran. Idea being to allow the compiler to optimize more aggressively.
Not specifically about making C more like Fortran, but there's been a lot of work over the years clarifying what compilers can and cannot assume. More recently, a lot of work going into things like 'pointer provenance', again in an effort to clarify where more aggressive optimizations can be done. And things like when can NULL checks be elided etc.
Some people resent all this and just want C to be more like a 'portable macro-assembler'.
Re: First official release of LLVM Flang
#17Re: First official release of LLVM Flang
#18> Whilst many alternative programming languages have come and gone, it [Fortran] has regained its popularity for writing high performance codes. I don't understand why sometimes people pluralize "code". It sounds a bit silly but maybe it's just me.
I'm seeing it here for the first time, and from multiple people. Maybe it's specific to the Fortran community?
Re: First official release of LLVM Flang
#19Yes, GNU now has a front end for COBOL, so LLVM turn. Maybe IBM and the Navy Department will help.
Re: First official release of LLVM Flang
#20Earlier quoted context omitted.
I'm seeing it here for the first time, and from multiple people. Maybe it's specific to the Fortran community?
It’s not, but it’s somewhat common among people making numerical models of dynamic systems and that sort of thing. People like Steve Brunton will often say all the “codes” are available to go along with his videos for example https://youtube.com/@eigensteve?si=IVLparAOZ9XDauTz