Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

requires perf information #102

Open
giuliomoro opened this issue Apr 1, 2023 · 1 comment
Open

requires perf information #102

giuliomoro opened this issue Apr 1, 2023 · 1 comment
Labels
documentation Improvements or additions to documentation good first issue Good for newcomers

Comments

@giuliomoro
Copy link
Contributor

If I build this patch

#N canvas 63 63 450 300 12;
#X obj 197 124 pow~;
#X obj 207 205 dac~;
#X obj 251 122 sqrt~;
#X connect 0 0 1 0;
#X connect 2 0 1 0;

I get

__sqrt~f requires perf information.
__pow~f requires perf information.

As part of a larger patch I have also seen

__cos~f requires perf information.

but I haven't been able to reproduce it by simply adding a [cos~] object.

Any idea what these are for?

@dromer
Copy link
Collaborator

dromer commented Apr 2, 2023

This information comes from the spec object: 446b30a

It gives information about specific instruction performance, which is used to calculate a total performance of the patch or at least some kind of profiling. It prints a table when you compile with verbose/-v option.

These are just warnings though, but I think it's because the perf section is missing: https://github.com/Wasted-Audio/hvcc/blob/develop/hvcc/core/json/heavy.ir.json#L763

@dromer dromer added the documentation Improvements or additions to documentation label Jun 26, 2023
@dromer dromer added the good first issue Good for newcomers label Jul 22, 2023
@dromer dromer added this to Review in Core Improvements Jul 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation good first issue Good for newcomers
Projects
Development

No branches or pull requests

2 participants