| View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
| 0012474 | CMake | CMake | public | 2011-09-22 12:41 | 2016-06-10 14:31 | ||||
| Reporter | Aaron Simmons | ||||||||
| Assigned To | Kitware Robot | ||||||||
| Priority | normal | Severity | major | Reproducibility | always | ||||
| Status | closed | Resolution | moved | ||||||
| Platform | any | OS | any | OS Version | any | ||||
| Product Version | CMake 2.8.5 | ||||||||
| Target Version | Fixed in Version | ||||||||
| Summary | 0012474: SWIG module should default to use -fno-strict-aliasing | ||||||||
| Description | SWIG has a pretty big gotcha buried in the docs: you have to know to pass -fno-strict-aliasing to gcc, otherwise crazy things might happen. It's documented here: http://www.swig.org/Doc2.0/Java.html#Java_compiling_dynamic [^] I think the SWIG module in CMake should default to using -fno-strict-aliasing. | ||||||||
| Steps To Reproduce | 1. Set up a C/C++ module that passes back a pointer. 2. Use CMake and SWIG to build a JNI library out of (1) 3. Write some Java code that uses the JNI library 4. Build the JNI library in release mode for Android 5. Boom Part (4) could be for any platform, but it happens most readily for Android. | ||||||||
| Additional Information | This SWIG gotcha has burned some people already: http://stackoverflow.com/questions/6753241/passing-pointer-from-c-to-java-becomes-null [^] While this isn't CMake's issue per se, I think if CMake implemented best practices for SWIG it would save everyone a lot of headaches. | ||||||||
| Tags | No tags attached. | ||||||||
| Attached Files | |||||||||
| Relationships | |
| Relationships |
| Notes | |
|
(0030308) David Cole (manager) 2012-08-11 11:38 |
Sending old, never assigned issues to the backlog. (The age of the bug, plus the fact that it's never been assigned to anyone means that nobody is actively working on it...) If an issue you care about is sent to the backlog when you feel it should have been addressed in a different manner, please bring it up on the CMake mailing list for discussion. Sign up for the mailing list here, if you're not already on it: http://www.cmake.org/mailman/listinfo/cmake [^] It's easy to re-activate a bug here if you can find a CMake developer who has the bandwidth to take it on, and ferry a fix through to our 'next' branch for dashboard testing. |
|
(0041906) Kitware Robot (administrator) 2016-06-10 14:28 |
Resolving issue as `moved`. This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page. |
| Notes |
| Issue History | |||
| Date Modified | Username | Field | Change |
| 2011-09-22 12:41 | Aaron Simmons | New Issue | |
| 2012-08-11 11:38 | David Cole | Status | new => backlog |
| 2012-08-11 11:38 | David Cole | Note Added: 0030308 | |
| 2016-06-10 14:28 | Kitware Robot | Note Added: 0041906 | |
| 2016-06-10 14:28 | Kitware Robot | Status | backlog => resolved |
| 2016-06-10 14:28 | Kitware Robot | Resolution | open => moved |
| 2016-06-10 14:28 | Kitware Robot | Assigned To | => Kitware Robot |
| 2016-06-10 14:31 | Kitware Robot | Status | resolved => closed |
| Issue History |
| Copyright © 2000 - 2018 MantisBT Team |