Generating a call tree For example, with this source we tell the profiler to generate a call tree instead of timings and counts. #cmdline "-profgen fb" #include once "fbc-int/profile.bi" fbc.ProfileSetOptions( fbc.PROFILE_OPTION_REPORT_CALLTREE ) sub A print "A" end sub...

Setting the output report file name at run-time New include file 'fbc-int/profile.bi' adds some API for working with profiling For example, this has the effect of setting the output filename for the profile report to "prof-hhmmss.txt" where 'hhmmss' is replaced with the current time: #incl...

Simple example, profiling a freebasic program and generating the default report: A simple example: #cmdline "-profgen fb" sub Pause100 sleep 100, 1 end sub sub Pause200 sleep 200, 1 end sub sub Pause400 sleep 400, 1 end sub for i as integer = 1 to 3 Pause100 next Pause200 Pause400 After co...

New command line option -profgen: 'fbc -profgen gmon' : enable profiling code generation for gmon/gprof 'fbc -profgen fb' : enable function call profiling using fb's profiler 'fbc -profgen cycles' : coming soon, for cpu cycle counting on some targets (currently a wip on -gen gas64 only) FYI on comma...

In latest fbc, added the first part for profiling freebasic programs.

Started a topic for this in the documentation sub forum:
Profiling freebasic programs

New profiling feature in freebasic '-profgen fb' command line option generates a profiling report "profile.txt" To try it out: - obtain latest fbc development binaries (or build your own) - add '#cmdline "-profgen fb"' to your source and compile your program - Or compile your pro...

For a guy that may be uncertain whether randomness actually exists, your response ... not what I expected. so I now learn that ' true random number generator' is a defined thing apparently ... which is not what I meant by 'true' (if that is what you thought). Anyway, my post intended to point out th...

I had to resolve to admit limits to optimization. In FB, I find it very difficult to see how the expected level of fragmentation tolerance could become, if necessary, a property of the syntax encapsulation of certain objects, but above all transparent from an algorithmic point of view... for a hypo...

When we do look outside, Schrödinger's wave equation collapses, and we will see rain 75% of the time. This is a variation of Schrödinger's cat. Oh, pish posh! The cat, the box, the observer, the inside and outside, are all part of one system (Everett's interpretation), so there is no collapse of th...

An update of some things being worked on... If we are going to make changes to string handling, (for example as discussed in this topic, temporary descriptors), I would like a way to conveniently profile the performance differences instead of having to write custom timing tests. Past couple of weeke...

Hello, when compiling this example using compiler 1.20.0 dated 04/01/2024, it gives the error: Since fbc version 1.20.0, Put# warns then crashes on compilation with an array as data. See posts above. (there are several recent changes regarding the arrays. Maybe : fbc: fix non-index array assignment...

adeyblue has the right idea. An audit will be worthwhile to identify all the junk. Some more aggressive concentrated effort than what we've been doing past several years of incremental reviews. Roadmap: Currently is a union of bug reports + TODO list + needs of developers of large fb projects + requ...

OK, I understand. I agree, this change it would be worthwhile to have some method to do both. When we made the big changes for name lookups we temporarily added a #pragma to allow old name lookup logic. We could do something similar for len/sizeof but to do 1 of 3 things: 1) old behaviour, 2) error ...

I don't think I have much thought about LEN(array) and SIZEOF(array). But even more the use of 'Len(array_name)' which is allowed (for the moment without a note in the documentation) is even more misleading because it actually always returns the value of 'Sizeof(array_element)' ! Yes, I see in compi...

I improved my code (to test the 'Byref' passing/returning to/from a function) without changing the output view: The 2 utility Sub's are transformed into macros and only the two main functions remain in the form of procedures (because, for a most reliable test possible of parameter passing, the veri...