sac2c issueshttps://gitlab.sac-home.org/sac-group/sac2c/-/issues2021-05-26T20:27:01Zhttps://gitlab.sac-home.org/sac-group/sac2c/-/issues/1016global objects inhibit fold functions2021-05-26T20:27:01ZSven-Bodo Scholzglobal objects inhibit fold functions| | |
| --- | --- |
| Bugzilla Link | [306](http://bugs.sac-home.org/show_bug.cgi?id=306) |
| Created on | Oct 12, 2006 10:59 |
| Version | 1.00beta |
| OS | SunOS |
| Architecture | PC |
## Extended Description
<pre>This bug is a co...| | |
| --- | --- |
| Bugzilla Link | [306](http://bugs.sac-home.org/show_bug.cgi?id=306) |
| Created on | Oct 12, 2006 10:59 |
| Version | 1.00beta |
| OS | SunOS |
| Architecture | PC |
## Extended Description
<pre>This bug is a conceptual problem but feels very much wrong...
if we introduce a print in a function used within a fold, the
subsequent change in signature inhibits the use as fold and thus leads
to a strange error message: ...function not found.....
Since all overloadings of a function are treated uniformly, the
offending print may even occur in a fold-irrelevant overloading only.
I am not sure how to handle this problem nicely:-(
I would assume that, in principle, this problem could be solved
in a rather complex modification of fold-wls using propagate or so.....</pre>BugZillaBugZillahttps://gitlab.sac-home.org/sac-group/sac2c/-/issues/2273Create a release2021-09-01T11:27:03ZHans-Nikolai ViessmannCreate a releaseIts been a while since we released a 'stable' version of sac2c. I don't see any reason to delay this, I think the compiler is pretty stable at the moment (seq, mt-pth, cuda targets seems to work fine).
Before we do this though, I think ...Its been a while since we released a 'stable' version of sac2c. I don't see any reason to delay this, I think the compiler is pretty stable at the moment (seq, mt-pth, cuda targets seems to work fine).
Before we do this though, I think there are a few things we should consider:
- [ ] what do we name it? _There hasn't been a devcamp in a while, so I guess we're going to have to get creative here..._
- [ ] decide on some schedule, or conditions to help us get into the habit of making releases more regularly (last stable release is 1.3.3-MijasCosta)
- [ ] in https://gitlab.sac-home.org/sac-group/sac2c/-/issues/2269#note_10870, @rbe makes a really good point regarding actually documenting the changes in the compiler (especially new features!). This would help making it more clear how much work is going into the compiler, and what research activities this is driving. For example, we have two presentations at IFL2021 talking about new features that are in the pipeline to be merged in a some point. I think adding a CHANGELOG file to the repo, and as part of a MR filling it in would go a long way. The changelog might also help in figuring out when to make a release (major or minor).
I probably missed out some things to consider, suggestions are welcome!!!Create a releaseHans-Nikolai ViessmannHans-Nikolai Viessmann