Timeline
2015-08-14:
- 15:58 Ticket #3402 (Build Environment - Fix GCC 5.x issues so that it can be used in Windows) updated by
- Partial fix in …
- 12:43 Ticket #3402 (Build Environment - Fix GCC 5.x issues so that it can be used in Windows) updated by
- Yes, I've copied them from here and did the diff: GCC 5.2.0: …
- 12:36 Ticket #3402 (Build Environment - Fix GCC 5.x issues so that it can be used in Windows) updated by
-
I've gone through all of those optimization, and
-O1 -f$optworks … - 11:29 Ticket #3402 (Build Environment - Fix GCC 5.x issues so that it can be used in Windows) updated by
- I have tried the omc with Matching.mo compiled with -O1 just on one …
- 10:31 Ticket #3408 (OMEdit - Unable to make connection from Modelica.Mechanics.MultiBody.Parts.PointMass) created by
- Graphically it is not possible to make connection from/to …
- 06:56 Ticket #3402 (Build Environment - Fix GCC 5.x issues so that it can be used in Windows) updated by
- If it's only Matching.mo, it is possible to script it. I could try in …
- 05:44 Ticket #3402 (Build Environment - Fix GCC 5.x issues so that it can be used in Windows) updated by
- The diffs between GCC 4.9.3 and GCC 5.2.0 with regards to -O2 …
- 05:20 Ticket #3402 (Build Environment - Fix GCC 5.x issues so that it can be used in Windows) updated by
- So is one of these that needs to be disabled (or a combination) for …
- 05:11 Ticket #3402 (Build Environment - Fix GCC 5.x issues so that it can be used in Windows) updated by
- Update: seems that if you compile Matching.mo with -O1 it works fine.
- 02:44 Ticket #3405 (Code Generation - Fix "implicit declaration" of functions) closed by
- invalid: This only happens for the code inside bootstrap-sources.tar.xz, not …
2015-08-13:
- 12:05 Ticket #3407 (*unknown* - Annex60 conversion script seems to need updates) updated by
- Same seems to hold true for Buildings library.
- 12:02 Ticket #3407 (*unknown* - Annex60 conversion script seems to need updates) created by
- As we can see here: https://test.openmodelica.org/libraries/trend.html …
- 09:02 Ticket #3406 (FMI - Problem with initial values / parameters in FMU generation from Simulink) updated by
- The attachment is missing. Attach the file using this link …
- 07:30 Ticket #3403 (Code Generation - Avoid using "time" as a macro variable) closed by
- fixed
- 07:30 Ticket #3403 (Code Generation - Avoid using "time" as a macro variable) updated by
-
Status, Owner, Milestone, Summary changed
- 07:29 Ticket #3403 (Code Generation - Avoid using "time" as a macro variable) updated by
- Should be fixed in …
- 07:24 Ticket #3406 (FMI - Problem with initial values / parameters in FMU generation from Simulink) created by
- Dear Sir/Madam, when generating FMUs with the Simulink coder target …
2015-08-12:
- 21:21 Ticket #3403 (Code Generation - Avoid using "time" as a macro variable) updated by
- I guess include change is to blame: …
- 19:43 Ticket #3403 (Code Generation - Avoid using "time" as a macro variable) updated by
- Seems also some models from PNLib are failing with this, i.e.: …
- 12:48 Ticket #3291 (Frontend - OMEdit: Simulation of Media.Examples.R134a produces Error) closed by
- fixed: Fixed in fd7495/OMCompiler
- 11:21 Ticket #3404 (OMEdit - Add an OMEdit menu option to open the working directory) updated by
-
Status changed
I could include option 1. I am not sure about option 2 but i will see … - 08:15 Ticket #3291 (Frontend - OMEdit: Simulation of Media.Examples.R134a produces Error) updated by
-
Status, Owner changed
- 08:12 Ticket #3291 (Frontend - OMEdit: Simulation of Media.Examples.R134a produces Error) updated by
-
Priority, Component changed
The same error shows up in the nightly tests. One reason is that … - 07:51 Ticket #3405 (Code Generation - Fix "implicit declaration" of functions) created by
- It seems that the .h file we include doesn't contain some functions …
- 07:07 Ticket #3404 (OMEdit - Add an OMEdit menu option to open the working directory) created by
- To make it easier for people to find the generated result files or to …
- 06:51 Ticket #3403 (Code Generation - Avoid using "time" as a macro variable) updated by
- Would probably be best to avoid using a macro named "time" regardless.
- 06:46 Ticket #3403 (Code Generation - Avoid using "time" as a macro variable) updated by
- As this library did not change then it means that some of the changes …
- 05:27 Ticket #3403 (Code Generation - Avoid using "time" as a macro variable) created by
- As far as I can see we define time in Model_model.h […] That has …
2015-08-11:
- 15:58 Ticket #3054 (OMEdit - Revert from previous unclear) updated by
- Well the message is not only shown when you are trying to save the …
- 06:17 Ticket #3402 (Build Environment - Fix GCC 5.x issues so that it can be used in Windows) updated by
-
Status, Owner changed
- 06:17 Ticket #3402 (Build Environment - Fix GCC 5.x issues so that it can be used in Windows) created by
- There are some tests failing when using GCC 5.x: …
2015-08-10:
- 23:36 Ticket #3401 (Interactive Environment - LeastSquares fails on GCC) updated by
- Running valgrind on it shows some issues: […]
- 23:35 Ticket #3401 (Interactive Environment - LeastSquares fails on GCC) updated by
-
Description changed
- 23:32 Ticket #3401 (Interactive Environment - LeastSquares fails on GCC) created by
- We have issues with dll function loading: …
- 06:34 Ticket #3400 (OMEdit - Multiple parameters with annotations in one line resulting in ...) created by
- I expierienced following bug in OMEdit. I definied several like four …
- 06:20 Ticket #3233 (Run-time - Simulation executable generated with +simCodeTarget=Cpp fails if ...) closed by
- fixed
- 06:20 Ticket #3233 (Run-time - Simulation executable generated with +simCodeTarget=Cpp fails if ...) updated by
-
Status, Owner changed
- 06:18 Ticket #3262 (Run-time - Translation error for MSL and OMEdit crash) closed by
- fixed: The example works now; maybe because omc pre-evaluates less functions …
- 06:09 Ticket #3286 (Run-time - Array storage order) closed by
- fixed
2015-08-07:
- 19:59 Ticket #3399 (Frontend - Add more granularity to function evaluation) updated by
- This is configuring which strategy to use to evaluate function calls. …
- 19:56 Ticket #3399 (Frontend - Add more granularity to function evaluation) updated by
- These are structural parameters and must be evaluated. No need to …
- 18:23 Ticket #3289 (FMI - FMU compilation (MSVC) fails for big models) updated by
- Hm, the MSDN says "The maximum length of a string literal is 65535 …
- 17:44 Ticket #3399 (Frontend - Add more granularity to function evaluation) updated by
- You need to evaluate certain parameters in order to determine array …
- 16:58 Ticket #3399 (Frontend - Add more granularity to function evaluation) updated by
- In mine the decisions should be based on the Modelica syntax as much …
- 15:07 Ticket #3289 (FMI - FMU compilation (MSVC) fails for big models) updated by
-
Status, Owner changed
If you define OPENMODELICA_XML_FROM_FILE_AT_RUNTIME when compiling the … - 10:17 Ticket #3399 (Frontend - Add more granularity to function evaluation) created by
- Currently, we have -d=gen and -d=evalFunc to control how to evaluate …
Note:
See TracTimeline
for information about the timeline view.
