Opened 12 years ago

Closed 4 years ago

Last modified 4 years ago

#2187 closed defect (fixed)

Evaluation of recursive functions during instantiation

Reported by: Christoph Höger Owned by: somebody
Priority: high Milestone: 1.16.0
Component: New Instantiation Version: trunk
Keywords: Cc:

Description

Hi all,

this model:

model Fak

  function f 
    input Real x;
    output Real y = if x < 1.0 then 1.0 else x * f(x-1);
  end f;

  Real x;
  Real y = 24;
  equation
  
  f(x) = y;

end Fak;

crashes during instantiation with a stackoverflow. Just two thoughts:

  • It seems like a bad idea in general to evaluate (recursive) functions at that time
  • At least omc should catch the stackoverflow and discard the attempted optimization IMO.

Attachments (1)

stacktrace (697.6 KB ) - added by Christoph Höger 12 years ago.
Stacktrace

Download all attachments as: .zip

Change History (13)

by Christoph Höger, 12 years ago

Attachment: stacktrace added

Stacktrace

comment:1 by Martin Sjölund, 12 years ago

It is not trying to do any optimisation as far as I know. It for sure did not try to evaluate the function.
It is just some weird dependency analysis gone haywire if the output binding of the function is recursive. The following works fine:

model Fak

  function f 
    input Real x;
    output Real y;
  algorithm
    y := if x < 1.0 then 1.0 else x * f(x-1);
  end f;

  Real x;
  Real y = 24;
  equation
  
  f(x) = y;

end Fak;
Version 0, edited 12 years ago by Martin Sjölund (next)

comment:2 by Martin Sjölund, 11 years ago

Milestone: 1.9.01.9.1

Postponed until 1.9.1

comment:3 by Martin Sjölund, 10 years ago

Milestone: 1.9.11.9.2

This ticket was not closed for 1.9.1, which has now been released. It was batch modified for milestone 1.9.2 (but maybe an empty milestone was more appropriate; feel free to change it).

comment:4 by Martin Sjölund, 10 years ago

Milestone: 1.9.21.9.3

Milestone changed to 1.9.3 since 1.9.2 was released.

comment:5 by Martin Sjölund, 9 years ago

Milestone: 1.9.31.9.4

Moved to new milestone 1.9.4

comment:6 by Martin Sjölund, 9 years ago

Milestone: 1.9.41.9.5

Milestone pushed to 1.9.5

comment:7 by Martin Sjölund, 9 years ago

Milestone: 1.9.51.10.0

Milestone renamed

comment:8 by Martin Sjölund, 8 years ago

Milestone: 1.10.01.11.0

Ticket retargeted after milestone closed

comment:9 by Martin Sjölund, 8 years ago

Milestone: 1.11.01.12.0

Milestone moved to 1.12.0 due to 1.11.0 already being released.

comment:10 by Francesco Casella, 7 years ago

Milestone: 1.12.0Future

The milestone of this ticket has been reassigned to "Future".

If you think the issue is still valid and relevant for you, please select milestone 1.13.0 for back-end, code generation and run-time issues, or 2.0.0 for front-end issues.

If you are aware that the problem is no longer present, please select the milestone corresponding to the version of OMC you used to check that, and set the status to "worksforme".

In both cases, a short informative comment would be welcome.

comment:11 by Per Östlund, 4 years ago

Component: FrontendNew Instantiation
Resolution: fixed
Status: newclosed

Works fine with the new frontend.

comment:12 by Francesco Casella, 4 years ago

Milestone: Future1.16.0
Note: See TracTickets for help on using tickets.