summaryrefslogtreecommitdiffstats
path: root/test
Commit message (Collapse)AuthorAgeFilesLines
* Fixed yet another small issue in test/efc.c.Dana Robinson2020-01-211-6/+6
|
* PATH_MAX fix in efc test for Windows.Dana Robinson2020-01-201-0/+5
|
* Merge branch 'develop' into stack_size_warningsDana Robinson2020-01-1735-1535/+6520
|\
| * Squashed commit of the token_refactoring branch:Dana Robinson2020-01-1633-1534/+6434
| |
| * Merge pull request #2237 in HDFFV/hdf5 from ~JSOUMAGNE/hdf5:HDFFV-10992-fix ↵Jerome Soumagne2020-01-151-0/+83
| |\ | | | | | | | | | | | | | | | | | | | | | to develop * commit 'a7648879d729c1b75bd32f3a151831e9cbfbe31c': Add test for reference shutdown issue H5R: set app ref when incrementing ref_count on location held by reference (fix HDFFV-10992)
| | * Add test for reference shutdown issueJerome Soumagne2020-01-151-0/+83
| | |
| * | HDFFV-11001 Add fine control over testingAllen Byrne2020-01-152-2/+4
| | |
* | | Tidying from code review.Dana Robinson2020-01-161-6/+20
| | |
* | | Fixed stack and frame size warnings. Not complete, but fixes most ofDana Robinson2020-01-1510-435/+977
|/ / | | | | | | the easier cases.
* | Modify external_env.c to prevent deleting test file of external.c.Larry Knox2020-01-091-2/+1
|/ | | | Fix for HDFFV-10941.
* Merge pull request #2071 in HDFFV/hdf5 from ~KMU/hdf5:bugfix/intel_warnings ↵Kimmy Mu2020-01-066-19/+19
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | to develop * commit '0a2bb11b248df6841daabca3970df5d8504adfc7': address problems from comments fix and address comments change according to previous comments add missing piece remove unnecessary check macro fix intel compile warnings Revert "fix warnings from Intel compiler" Revert "fix warnings and some text alignment" Revert "let hdf5 pick up the right compiler in Intel environment" Revert "fix issues from previous PR comments" Revert "using a different MACRO" using a different MACRO fix issues from previous PR comments let hdf5 pick up the right compiler in Intel environment fix warnings and some text alignment fix warnings from Intel compiler
| * address problems from commentskmu2019-12-111-2/+0
| |
| * fix and address commentskmu2019-12-112-7/+10
| |
| * Merge branch 'develop' into bugfix/intel_warningskmu2019-12-0943-329/+264
| |\
| * | remove unnecessary check macrokmu2019-12-063-8/+7
| | |
| * | fix intel compile warningskmu2019-12-046-16/+16
| | |
| * | Oops, remove more C99 designated initializers for VS 2010 compatibility.David Young2019-11-251-2/+6
| | |
| * | Add new source files to CMakeLists.txt.David Young2019-11-201-0/+2
| | |
| * | free -> HDfreeDavid Young2019-11-201-1/+1
| | |
| * | Quiet decleration-after-statement warnings.David Young2019-11-131-5/+4
| | |
| * | Undo accidental test deletion.David Young2019-11-131-1/+1
| | |
| * | Oops, delete a debug printf that snuck in here.David Young2019-11-131-1/+0
| | |
| * | Change hdset_reg_ref_t and H5R_ref_t from arrays of unsigned char toDavid Young2019-11-132-134/+139
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | structs containing those arrays. Encapsulating the arrays in this way makes it easier to write and think about pointers to these types, casts to/from these types, etc. An interesting side-effect that we probably should *not* rely on is that the struct-encapsulation changes the alignment so that some GCC warnings about casts that increase the alignment requirement of the operand go away. Warnings like that have to be taken seriously: I will add -Werror=cast-align to the default compiler flags so that they stop the build quickly. GCC warnings led me to some surprising casts in test/trefer.c. I found that it was possible to make many simplifications after introducing the struct-encapsulation that I described, above.
| * | In every instance, `x` is initialized by `memcpy`, but GCC isn't smartDavid Young2019-11-131-17/+17
| | | | | | | | | | | | | | | enough to figure that out. Quiet some warnings by always initializing `x` to 0.
| * | `same_file` is assigned but never used. Delete it.David Young2019-11-131-8/+0
| | |
| * | Don't assign a constant string to a pointer to non-constant character.David Young2019-11-131-1/+1
| | |
| * | GCC isn't smart enough to realize that `fill_c` is always initializedDavid Young2019-11-131-1/+2
| | | | | | | | | | | | | | | and exclusively used in `datatype == H5T_COMPOUND` branches, so just initialize it at its declaration so that GCC doesn't warn.
| * | I'm not sure what the previous code was trying to do, casting an arrayDavid Young2019-11-131-2/+2
| | | | | | | | | | | | | | | | | | of `hsize_t`, `start`, to `long long`, but I think the way that I have rewritten it, it probably produces a more useful result? As a bonus, GCC has stopped warning about it.
| * | Quiet a warning about an unused variable. This code looks like itDavid Young2019-11-131-1/+1
| | | | | | | | | | | | | | | should be heavily restructured to avoid the use of globals like `pass`, but that's a project for another day and another person.
| * | Straggler from previous commit: build and link the new .c files where IDavid Young2019-11-131-1/+7
| | | | | | | | | | | | | | | moved some previously-static variables and functions that were causing unused-variable/function warnings.
| * | Move some static functions and variables to .c files to avoid unusedDavid Young2019-11-134-54/+106
| | | | | | | | | | | | function/variable warnings.
| * | Avoid unused-variable warnings: change static const strings in a coupleDavid Young2019-11-131-1/+1
| | | | | | | | | | | | of header-file templates to #defines.
| * | Merge remote-tracking branch 'hdf5/develop' into add-werror-and-squash-some toDavid Young2019-11-121-32/+121
| |\ \ | | | | | | | | | | | | see if new warnings-as-errors have cropped up.
| * \ \ Merge remote-tracking branch 'hdf5/develop' into add-werror-and-squash-someDavid Young2019-11-081-1/+7
| |\ \ \ | | | | | | | | | | | | | | | to pick up the NetBSD-compatibility changes that I recently merged.
| * | | | Change some GCC warnings to errors. Fix code to quiet some warnings.David Young2019-11-057-14/+28
| | | | |
* | | | | Small changes from the token_refactoring branch, to reduce the delta to developQuincey Koziol2020-01-0414-359/+476
| | | | |
* | | | | Refactor H5Dvlen_get_buf_size to use optional dataset operation, with ↵Quincey Koziol2019-12-211-3/+3
| | | | | | | | | | | | | | | | | | | | generic fallback for VOL connectors that don't implement operation
* | | | | Refactor all the 'H5VL_*_optional' callbacks to move the type of operation outQuincey Koziol2019-12-203-12/+32
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | of the va_list, so it's at least possible for another connector to know what the operation is and decide whether to implement it or not. Added a new VOL sub-class called "introspect" where callbacks that report information about the connector or container can be placed. Added an 'opt_query' callback to this sub-class, for a connector to report back to the library whether a particular optional callback operation is supported. Also added a 'get_conn_cls' introspection callback, to retrieve the H5VL_class_t of a connector (either the "current" connector, H5VL_GET_CONN_LVL_CURR, or the terminal connector, H5VL_GET_CONN_LVL_TERM). Moved the "post open" operation from a file 'specific' operation to a file 'optional' operation, now that it's possible to detect (with the 'opt_query' introspection callback) whether a VOL connector implements an optional operation, without just returning an error. Added new internal VOL helper routines: H5VL_object_is_native, to determine if an object is in (or is a) native file, and H5VL_file_is_same, to determine if two objects are in (or are) the same terminal VOL connector's container. (And moved the special handling for FILE_IS_EQUAL operation out of internal VOL callback routine into H5VL_file_is_same) Made new dataset 'get' operation for H5Dvlen_get_buf_size, aligning it better with other 'get' operations in API. Fixed several issues with pass-through connectors, which are now passing the 'make check-passthrough-vol' tests again. A bunch of warning and style cleanups as well.
* | | | | Remove constAllen Byrne2019-12-181-1/+1
| | | | |
* | | | | Fix compile error - declaration after executable statementAllen Byrne2019-12-181-2/+3
| | | | |
* | | | | Adjust cache.c only variables.Allen Byrne2019-12-183-29/+26
| | | | |
* | | | | Fix include to correct memory calls - big-endian issue.Allen Byrne2019-12-182-1/+1
| | | | |
* | | | | Merge pull request #2086 in HDFFV/hdf5 from ↵Vailin Choi2019-12-161-1/+1
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ~VCHOI/my_third_fork:bugfix/reference_ver_hyperslab_ver to develop * commit 'b42325e8f5ff3b6bfa2ce446af5b6dc5cbbff666': More fixes for previous committed PR #2079 dated Dec 5 2019. (1) H5O_dtype_ver_bounds[] for V112 should be H5O_DTYPE_VRESION_4 (2) The tests for the new reference types should work for V112 and beyond
| * | | | | More fixes for previous committed PR #2079 dated Dec 5 2019.Vailin Choi2019-12-061-1/+1
| | |_|_|/ | |/| | | | | | | | | | | | | | | | | | (1) H5O_dtype_ver_bounds[] for V112 should be H5O_DTYPE_VRESION_4 (2) The tests for the new reference types should work for V112 and beyond
* | | | | HDFFV-10979 cleanup globalsAllen Byrne2019-12-122-7/+5
| | | | |
* | | | | HDFFV-10979 fix global name clashAllen Byrne2019-12-114-718/+727
|/ / / /
* | | | Merge pull request #2076 in HDFFV/hdf5 from ~JSOUMAGNE/hdf5:type_fixes to ↵Jerome Soumagne2019-12-053-142/+139
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | develop * commit '7b03a1c03633d695b487642e54f897c715f8622e': Fix H5VL_token_t type and fix H5VL_loc_by_token to use H5VL_token_t * Change hdset_reg_ref_t and H5R_ref_t from arrays of unsigned char to structs containing those arrays. Encapsulating the arrays in this way makes it easier to write and think about pointers to these types, casts to/from these types, etc.
| * | | | Change hdset_reg_ref_t and H5R_ref_t from arrays of unsigned char toDavid Young2019-12-053-142/+139
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | structs containing those arrays. Encapsulating the arrays in this way makes it easier to write and think about pointers to these types, casts to/from these types, etc. An interesting side-effect that we probably should *not* rely on is that the struct-encapsulation changes the alignment so that some GCC warnings about casts that increase the alignment requirement of the operand go away. Warnings like that have to be taken seriously: I will add -Werror=cast-align to the default compiler flags so that they stop the build quickly. GCC warnings led me to some surprising casts in test/trefer.c. I found that it was possible to make many simplifications after introducing the struct-encapsulation that I described, above. In test objcopy_ref `same_file` is assigned but never used. Delete it.
* | | | | Two fixes:Vailin Choi2019-12-051-1/+1
|/ / / / | | | | | | | | | | | | | | | | (1) Set the version for reference datatype messge to H5O_DTYPE_VERSION_4. (2) Verify the decoded version for hyperslab selection.
* | | | Yanked -Wc++-compat from the flags used to build the C library in bothDana Robinson2019-12-0424-112/+112
| | | | | | | | | | | | | | | | the Autotools and CMake.
generated by cgit v0.12 at 2024-11-01 20:03:28 (GMT)