-
Notifications
You must be signed in to change notification settings - Fork 169
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
Windows: MSVC: Allocate wave_slice_dq array using mem_alloc_dq() #7491
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CI is also failing on master
, so the failures here probably unrelated.
68f1550
to
3b3a76f
Compare
Codecov ReportPatch and project coverage have no change.
Additional details and impacted files@@ Coverage Diff @@
## master #7491 +/- ##
=======================================
Coverage 77.56% 77.56%
=======================================
Files 452 452
Lines 36211 36211
=======================================
Hits 28086 28086
Misses 8125 8125
*This pull request uses carry forward flags. Click here to find out more. Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
824ede4
to
867d495
Compare
867d495
to
b6e9f22
Compare
I have a similar fix to some other cube_build updates on a branch I am working on and I have tested it quite a lot. This fix cleans up the remaining memory leaks. |
I do not think the old code could have resulted in a memory leak but allocating large arrays on stack is not a good idea in general and allocating variable size arrays is not supported by all compilers (not a standard C feature depending on the standard version). For MS, in particular see https://devblogs.microsoft.com/cppblog/c11-and-c17-standard-support-arriving-in-msvc/#variable-length-arrays |
Running on a Mac M1 computer - the memory is smaller now than before the change to the dq arrays. |
Just merge this already! 😸 |
I have a pr with exactly the same updates + other stuff. So if you merge this one I will rebase my code to grab you merge. It would helpful to merge this one soon because I want to submit my pr today and I can get it clean up with including this pr before I do that. |
I don't have the power. Otherwise, I would have done it already. 😸 |
cube_build | ||
---------- | ||
|
||
- Windows: MSVC: Allocate ``wave_slice_dq`` array using ``mem_alloc_dq()`` [#7491] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just curious, what does MSVC stand for?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Comment could be improved
Thanks! |
@zacharyburnett , are you sure jwst won't work on Windows? Though hard to tell without actually running CI on it. |
Oh nice, I didn't know about this! Shows what I know haha 😅 I can add some CI tests to the weekly cron to see how stable Windows support is EDIT: made a PR #7562 |
Resolves N/A
Closes #6466, closes #6905
Related: #5578, spacetelescope/crds#790 (comment)
This replaces two variable length array declarations that are preventing Microsoft CL from succeeding. (Refer to #6466 above.)
I tested locally with:
PS - I also noticed drizzle-1.13.7 fails to build on Windows, however at the time of this writing
drizzle/master
anddrizzle/1.13.7
are the same... yetpip install git+https://github.com/spacetelescope/drizzle
actually succeeds. Very strange. Maybe the archive is missing something?Checklist for maintainers
CHANGES.rst
within the relevant release sectionHow to run regression tests on a PR