Welcome to mirror list, hosted at ThFree Co, Russian Federation.

git.blender.org/blender.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2021-06-26Cleanup: full sentences in comments, improve comment formattingCampbell Barton
2020-11-25Fluid Particles: fix viscoelastic spring threading crash again after D7394.Alexander Gavrilov
Since D6133 fluid particle code uses thread local storage to collect springs created during a time step before adding them to the actual spring array. Prior to the switch to TBB there was a single finalize callback which was called on the main thread, so it could use psys_sph_flush_springs and insert the new entries into the final buffer. However in D7394 it was replaced with a reduce callback, which is supposed to be thread safe and have no side effects. This means that the only thing it can safely do is copy entries to the other temporary buffer. In addition, careful checking reveals that the 'classical' solver doesn't actually add springs, so reduce isn't needed there. Differential Revision: https://developer.blender.org/D9632
2020-08-07Code Style: use "#pragma once" in source directoryJacques Lucke
This replaces header include guards with `#pragma once`. A couple of include guards are not removed yet (e.g. `__RNA_TYPES_H__`), because they are used in other places. This patch has been generated by P1561 followed by `make format`. Differential Revision: https://developer.blender.org/D8466
2020-03-02Cleanup: make remaining blenlib headers work in C++Jacques Lucke
Differential Revision: https://developer.blender.org/D6988 Reviewers: brecht
2019-11-09Fluid Particles: fix threading crash with viscoelastic springs.Alexander Gavrilov
As correctly pointed out by a comment in the code, adding new springs wasn't thread safe, and caused crashes. Fix by buffering new springs in intermediate thread-local arrays, which are flushed on the main thread. This is valid because the new springs are not used until the next sim step. Differential Revision: https://developer.blender.org/D6133
2019-05-23Cleanup: allow BLI_Buffer to be used without it's headerCampbell Barton
Without this any functions declared that take BLI_Buffer also needed to include the header.
2019-04-17ClangFormat: apply to source, most of internCampbell Barton
Apply clang format as proposed in T53211. For details on usage and instructions for migrating branches without conflicts, see: https://wiki.blender.org/wiki/Tools/ClangFormat
2019-02-18doxygen: add newline after \fileCampbell Barton
While \file doesn't need an argument, it can't have another doxy command after it.
2019-02-06Cleanup: remove redundant doxygen \file argumentCampbell Barton
Move \ingroup onto same line to be more compact and make it clear the file is in the group.
2019-02-01Cleanup: remove redundant, invalid info from headersCampbell Barton
BF-admins agree to remove header information that isn't useful, to reduce noise. - BEGIN/END license blocks Developers should add non license comments as separate comment blocks. No need for separator text. - Contributors This is often invalid, outdated or misleading especially when splitting files. It's more useful to git-blame to find out who has developed the code. See P901 for script to perform these edits.
2018-02-01Cleanup: rename BLI_*_empty() -> clear()Campbell Barton
Consistent with other BLI API's
2015-12-23Remove BLI_buffer calloc optionCampbell Barton
This wasn't working reliably (after clear for example), and wasn't used anywhere.
2015-10-04Correct last commit, picky type warningsCampbell Barton
2015-10-04BLI_Buffer: add BLI_buffer_reinitCampbell Barton
Useful for re-using a buffer when the existing data can be thrown away.
2015-10-04BLI_Buffer: support over 2gb allocationsCampbell Barton
Also move comment to C-source and enumerate useful features.
2015-02-14cleanup: doxy commentsCampbell Barton
2014-10-10BLI_buffer: empty macroCampbell Barton
2013-09-12code cleanup: headers - doxy comments.Campbell Barton
2013-08-07code cleanup: more confusion with 0/NULL/falseCampbell Barton
2013-07-26fix for error in BLI_buffer_declare_static(), the stack variable wasn't the ↵Campbell Barton
right size, from original commit 53440. Caused UV stretch display to fail.
2013-03-16changes to BLI_bufferCampbell Barton
- assert if BLI_buffer_at() is called with an out of bounds value. - add BLI_buffer_resize_data() macro which resizes and returns a pointer to the new array. - warn if missing call to BLI_buffer_free().
2013-01-02add assert to BLI_buffer_at if a type is given different to 'elem_size'Campbell Barton
2013-01-02extend BLI_bufferCampbell Barton
- add option to calloc or not, existing code wasnt consistent here, would calloc on first alloc but not on realloc, also - the static memory was never zero'd. use flag BLI_BUFFER_USE_CALLOC to ensure all new memory is zero'd (static/alloc/realloc's). - add BLI_buffer_declare_static / BLI_buffer_declare so its possible to have a buffer that never uses static memory.
2012-12-30Add BLI_buffer, an alternative to BLI_arrayNicholas Bishop
BLI_buffer is a dynamic homogeneous array similar to BLI_array, but it allocates a structure that can be passed around making it possible to resize the array outside the function it was declared in.