Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8083201 | emb-9 | Kim Barrett | P4 | Resolved | Fixed | team |
Begin the process of eliminating the name clash between the VM's assert() macro and the standard (<assert.h> / <cassert>) assert() macro.
This first step is to rename assert() to vmassert(), but continue to provide an assert() synonym for backward compatibility. This renaming should be back-ported to earlier versions, to simplify backporting of other changes.
Once this change and the associated back-porting has been completed, we can incrementally change uses of assert => vmassert in the latest development trees. Once that renaming has been completed, we can remove the backward compatibility synonym from the latest development trees.
This first step is to rename assert() to vmassert(), but continue to provide an assert() synonym for backward compatibility. This renaming should be back-ported to earlier versions, to simplify backporting of other changes.
Once this change and the associated back-porting has been completed, we can incrementally change uses of assert => vmassert in the latest development trees. Once that renaming has been completed, we can remove the backward compatibility synonym from the latest development trees.
- backported by
-
JDK-8083201 Rename assert() to vmassert()
-
- Resolved
-
- blocks
-
JDK-8007770 fix name clash of assert macro in debug.hpp with libc's assert macro
-
- Closed
-
- relates to
-
JDK-8007770 fix name clash of assert macro in debug.hpp with libc's assert macro
-
- Closed
-