On Fri, 15 Nov 2024 14:50:21 GMT, Magnus Ihse Bursie wrote:
>> Currently, the man pages are stored as troff (a text format) in the open
>> repo, and a content-wise identical copy is stored as markdown (another text
>> format) in the closed repo.
>>
>> Since markdown is preferred to troff in te
> [JDK-8305590](https://bugs.openjdk.org/browse/JDK-8305590) removed
> `-fcheck-new` when building with gcc. It turns out Visual Studio has a
> similar option, though inverted in behavior and default.
>
> It seems like /Zc:throwingNew- (the default) corresponds to gcc -fcheck-new,
> and /Zc:thr
On Sun, 17 Nov 2024 06:13:46 GMT, Phil Race wrote:
>> [JDK-8305590](https://bugs.openjdk.org/browse/JDK-8305590) removed
>> `-fcheck-new` when building with gcc. It turns out Visual Studio has a
>> similar option, though inverted in behavior and default.
>>
>> It seems like /Zc:throwingNew- (t
On Sun, 17 Nov 2024 09:22:40 GMT, Kim Barrett wrote:
>> src/java.desktop/windows/native/libawt/windows/awt_new.cpp line 127:
>>
>>> 125: }
>>> 126: #endif
>>> 127:
>>
>> I don't see you commenting on this which is a "huge" deal as it seems like
>> it changes memory allocation for a lot of the
On Tue, 12 Nov 2024 14:30:05 GMT, Julian Waters wrote:
> [JDK-8305590](https://bugs.openjdk.org/browse/JDK-8305590) removed
> `-fcheck-new` when building with gcc. It turns out Visual Studio has a
> similar option, though inverted in behavior and default.
>
> It seems like /Zc:throwingNew- (th
