On 6/14/23 16:09, Pali Rohár wrote:
It adjust preprocess, compile and link flags, which allows to change
default -lmsvcrt library by another provided by MinGW runtime.
gcc/
* config/i386/mingw-w64.h (CPP_SPEC): Adjust for -mcrtdll=.
(REAL_LIBGCC_SPEC): New define.
* config/i386
On 6/12/23 01:26, LIU Hao wrote:
在 2023/6/12 07:08, Jonathan Yong 写道:
+preprocessor is done. MinGW import library @code{msvcrt} is just a
+symlink (or file copy) to the other MinGW CRT import library
I suggest a change to this line:
symlink to (or a copy of) another MinGW CRT import libr
On 5/27/23 10:14, Pali Rohár wrote:
It adjust preprocess, compile and link flags, which allows to change
default -lmsvcrt library by another provided by MinGW runtime.
gcc/
* config/i386/mingw-w64.h (CPP_SPEC): Adjust for -mcrtdll=.
(REAL_LIBGCC_SPEC): New define.
* config/i386
On 6/5/23 09:22, Costas Argyris wrote:
Thanks, here is the follow up patch for a couple typos in the same file.
Thanks, pushed as obvious.
On 5/23/23 08:21, Jonathan Yong wrote:
On 5/22/23 13:25, Costas Argyris wrote:
Currently on Windows, when CreateProcess is called with a command-line
that exceeds the 32k Windows limit, we get a very bad error:
"CreateProcess: No such file or directory"
This patch detects the case where this w
On 5/22/23 13:25, Costas Argyris wrote:
Currently on Windows, when CreateProcess is called with a command-line
that exceeds the 32k Windows limit, we get a very bad error:
"CreateProcess: No such file or directory"
This patch detects the case where this would happen and writes the
long command-
On 4/12/23 13:39, Costas Argyris wrote:
This is proposed to fix PR109460 where an older version of
gcc (7.3) was used to build for windows (mingw) host.
Thanks, accepted and pushed to master branch.
On 3/31/23 00:09, Mike Stump wrote:
On Feb 27, 2023, at 2:29 AM, Jonathan Yong via Gcc-patches
wrote:
Attached patch OK?
Ok.
* c-c++-common/Warray-bounds.c: Fix excess warnings on
LLP64.<0001-c-c-common-Warray-bounds.c-fix-excess-warnings-on-LL.pa
On 2/27/23 10:29, Jonathan Yong wrote:
Attached patch OK?
Excess errors on x86_64-w64-mingw32:
/home/user/p/gcc/src/gcc-git/gcc/testsuite/c-c++-common/Warray-bounds.c:50:3: warning: array subscript 4611686018427387902 is above array bounds of 'struct S16[]' [-Warray-bounds=]
/ho
On 3/28/23 10:43, Costas Argyris wrote:
I forgot to update the relevant comments with the previous patch.
This is a comment-only patch that brings them up-to-date.
Done, thanks.
On 3/27/23 17:17, Costas Argyris wrote:
The patch attached to this email extends the UTF-8 support of the
driver and compiler processes to the 32-bit mingw host.Initially,
only the 64-bit host got it.
About the changes in sym-mingw32.cc:
Even though the 64-bit host was building fine with th
On 3/12/23 16:54, Jeff Law wrote:
Windows code is effectively always PIC, since the PE loader can
relocate it anywhere if the preferred address is already occupied.
Patch still OK?
Yes, still OK. Just make the trivial ChangeLog adjustments.
Done, pushed to master branch, thanks.
On 3/11/23 17:29, Jeff Law wrote:
On 2/14/23 03:42, Jonathan Yong via Gcc-patches wrote:
Attached patches OK?
0002-gcc-testsuite-gcc.dg-fix-pic-test-case-for-PE-target.patch
From 616e43ac41879040e73a266065874148553cddcc Mon Sep 17 00:00:00 2001
From: Jonathan Yong<10wa...@gmail.com>
On 3/10/23 09:37, Jakub Jelinek wrote:
Hi!
I'd like to ping this patch (as I wrote a week ago, NightStrike has tested
it):
Thanks, pushed to master branch.
On 3/9/23 13:33, Costas Argyris wrote:
Pinging the list and mingw maintainer.
Analysis and pre-approval here:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108865
Thanks, pushed to master branch.
On 3/2/23 10:46, Richard Sandiford wrote:
diff --git a/gcc/testsuite/gcc.dg/memchr-3.c b/gcc/testsuite/gcc.dg/memchr-3.c
index c38d9cf3349..af1b26ef3ae 100644
--- a/gcc/testsuite/gcc.dg/memchr-3.c
+++ b/gcc/testsuite/gcc.dg/memchr-3.c
@@ -6,7 +6,7 @@
typedef __INT8_TYPE__ int8_t;
typedef __I
On 3/2/23 10:44, Richard Sandiford wrote:
diff --git a/gcc/testsuite/gcc.dg/overflow-warn-9.c
b/gcc/testsuite/gcc.dg/overflow-warn-9.c
index 57c0f17bc91..ae588bd8491 100644
--- a/gcc/testsuite/gcc.dg/overflow-warn-9.c
+++ b/gcc/testsuite/gcc.dg/overflow-warn-9.c
@@ -59,7 +59,8 @@ const struct Ty
On 3/1/23 09:21, Richard Biener wrote:
On Wed, Mar 1, 2023 at 9:52 AM NightStrike via Gcc-patches
wrote:
On Thu, Feb 16, 2023, 11:10 LIU Hao via Gcc-patches
wrote:
--
Best regards,
LIU Hao
Ping
OK.
Done, pushed to master branch.
On 2/28/23 18:15, Jakub Jelinek wrote:
On Wed, Feb 15, 2023 at 01:44:08PM +, Jonathan Yong via Gcc-patches wrote:
gcc/testsuite/ChangeLog:
* gcc.target/i386/harden-sls-6.c: fix warning on LLP64
targets.
Attached patch OK?
From c0572a1e95c6f569980d6b7454c8dc293f07389e
On 2/27/23 16:55, Richard Sandiford wrote:
Jonathan Yong via Gcc-patches writes:
Attached patch OK?
gcc.dg/memchr-3.c: fix for LLP64
gcc/testsuite/ChangeLog:
PR middle-end/97956
* gcc.dg/memchr-3.c (memchr): fix long to size_t in
On 2/28/23 03:06, Hans-Peter Nilsson wrote:
On Mon, 27 Feb 2023, Jonathan Yong via Gcc-patches wrote:
This test is for LP64 only, exclude LLP64 too.
Patch OK?
I may be confused, but you're not making use of the "llp64"
effective target, there instead excluding/including lp64
On 2/28/23 02:10, Hans-Peter Nilsson wrote:
On Sun, 26 Feb 2023, Jonathan Yong via Gcc-patches wrote:
Patch OK for master branch? I did not see any obvious issues to exclude LLP64
specifically.
I see "lp64 || lp64" in that patch (which should preferably have
been sent inline, as i
Attached patch OK?
Excess errors on x86_64-w64-mingw32:
/home/user/p/gcc/src/gcc-git/gcc/testsuite/c-c++-common/Warray-bounds.c:50:3:
warning: array subscript 4611686018427387902 is above array bounds of 'struct
S16[]' [-Warray-bounds=]
/home/user/p/gcc/src/gcc-git/gcc/testsuite/c
Attached patch OK?
gcc.dg/memchr-3.c: fix for LLP64
gcc/testsuite/ChangeLog:
PR middle-end/97956
* gcc.dg/memchr-3.c (memchr): fix long to size_t in
prototype.
From 194eb3d43964276beeaea14ebee4b241799cd966 Mon Sep 17 00:00:00 2001
From: Jonath
This test is for LP64 only, exclude LLP64 too.
Patch OK?From fbc83ae10df1a0e10c302fb0fee13092eb65818e Mon Sep 17 00:00:00 2001
From: Jonathan Yong <10wa...@gmail.com>
Date: Mon, 27 Feb 2023 09:49:31 +
Subject: [PATCH] gcc.dg/overflow-warn-9.c: exclude from LLP64
gcc/testsuite/ChangeLog:
* g
Patch OK for master branch? I did not see any obvious issues to exclude
LLP64 specifically.From 9c770936c4c6ffb59d15e5c1ce331494ba102250 Mon Sep 17 00:00:00 2001
From: Jonathan Yong <10wa...@gmail.com>
Date: Sun, 26 Feb 2023 06:34:04 +
Subject: [PATCH] gcc.c-torture/compile/103818.c: enable fo
On 2/22/23 09:25, Jakub Jelinek wrote:
Hi!
As discussed in the PR, t-cygwin-w64 file has been introduced in 2013
and has one important problem, two different multilib options -m64 and -m32,
but MULTILIB_DIRNAMES with just one word in it.
Before the genmultilib sanity checking was added, my under
On 2/22/23 09:25, Jakub Jelinek wrote:
Hi!
As discussed in the PR, t-cygwin-w64 file has been introduced in 2013
and has one important problem, two different multilib options -m64 and -m32,
but MULTILIB_DIRNAMES with just one word in it.
Before the genmultilib sanity checking was added, my under
gcc/testsuite/ChangeLog:
* gcc.target/i386/harden-sls-6.c: fix warning on LLP64
targets.
Attached patch OK?From c0572a1e95c6f569980d6b7454c8dc293f07389e Mon Sep 17 00:00:00 2001
From: Jonathan Yong <10wa...@gmail.com>
Date: Wed, 15 Feb 2023 13:42:12 +
Subject: [PATCH] harden-
Attached patches OK?From 616e43ac41879040e73a266065874148553cddcc Mon Sep 17 00:00:00 2001
From: Jonathan Yong <10wa...@gmail.com>
Date: Tue, 14 Feb 2023 10:37:03 +
Subject: [PATCH 2/2] gcc/testsuite/gcc.dg: fix pic test case for PE targets
gcc/testsuite/ChangeLog:
* pic-2.c: fix expected _
On 2/13/23 07:04, Jeff Law wrote:
On 1/28/23 11:16, Jonathan Yong via Gcc-patches wrote:
Patch OK?
gcc/testsuite/ChangeLog:
* gcc.dg/pr65658.c: fix LLP64 test.
0001-pr65658.c-fix-excess-warnings-on-LLP64-targets.patch
From bd2634e2795723f290dcf4bbb06e70fb6ca6af51 Mon Sep 17 00:00:00
On 2/13/23 06:28, Jeff Law wrote:
On 2/11/23 01:33, Jonathan Yong via Gcc-patches wrote:
Attached patch OK?
0001-builtin-declaration-mismatch-7-fix-LLP64-targets.patch
From 3ba6812366e837a87c15360e83d1f72ffdd29684 Mon Sep 17 00:00:00 2001
From: Jonathan Yong<10wa...@gmail.com>
Dat
On 2/11/23 08:52, Gerald Pfeifer wrote:
On Sat, 11 Feb 2023, Jonathan Yong via Gcc-patches wrote:
could you please close the corresponding BR too?:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108350
I can't close it, but I put a note that it has been committed.
I closed the report.
G
On 2/11/23 07:28, i.nix...@autistici.org wrote:
Thank you Jonathan!
could you please close the corresponding BR too?:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108350
best!
I can't close it, but I put a note that it has been committed.
Attached patch OK?From 3ba6812366e837a87c15360e83d1f72ffdd29684 Mon Sep 17 00:00:00 2001
From: Jonathan Yong <10wa...@gmail.com>
Date: Sat, 11 Feb 2023 08:30:55 +
Subject: [PATCH] builtin-declaration-mismatch-7: fix LLP64 targets
gcc/testsuite/ChangeLog:
* gcc.dg/Wbuiltin-declaration-mismat
On 2/6/23 06:40, Jonathan Yong wrote:
On 1/18/23 10:44, i.nixman--- via Gcc-patches wrote:
hello again!
the final version of the path for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108350
successfully bootstraped for x86_64-mingw32 and x86_64-linux.
could anyone apply it please?
best!
On 1/18/23 10:44, i.nixman--- via Gcc-patches wrote:
hello again!
the final version of the path for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108350
successfully bootstraped for x86_64-mingw32 and x86_64-linux.
could anyone apply it please?
best!
Looks good to me, please supply the a
Patch OK?
gcc/testsuite/ChangeLog:
* gcc.dg/pr65658.c: fix LLP64 test.From bd2634e2795723f290dcf4bbb06e70fb6ca6af51 Mon Sep 17 00:00:00 2001
From: Jonathan Yong <10wa...@gmail.com>
Date: Sat, 28 Jan 2023 18:12:50 +
Subject: [PATCH] pr65658.c: fix excess warnings on LLP64 targets
gcc
I'm not fully confident if it might break other platforms. So hopefully
someone can comment on the patch.
gcc/testsuite/ChangeLog:
* c-c++-common/Wsizeof-array-div1.c: fix excess warnings.
* gcc.dg/Warray-bounds-52.c: ditto
* gcc.dg/Wstringop-overflow-62.c: ditto
On 1/19/23 09:26, Jonathan Yong wrote:
On 1/11/23 09:56, Jonathan Yong wrote:
Are the patches and changelogs OK?
Ping1.
Pushed to master branch.
On 1/11/23 09:56, Jonathan Yong wrote:
Are the patches and changelogs OK?
Ping1.
On 1/14/23 20:39, Jonathan Wakely wrote:
OK for trunk?
Looks OK to me, thanks for the patch.
On 1/12/23 21:10, Jonathan Wakely wrote:
Tested x86_64-linux. Bootstrapped x86_64-w64-mingw32 with both
--enable-threads=posix and --enable-threads=win32.
I need a libgcc or mingw maintainer to approve the gthr-win32.h part.
OK for trunk?
Looks good to me even if its a dummy member. Thanks f
Are the patches and changelogs OK?From 6edfba9e9a5f8fddc45d137b9f2d07c7f9065eaa Mon Sep 17 00:00:00 2001
From: Jonathan Yong <10wa...@gmail.com>
Date: Sun, 8 Jan 2023 01:28:34 +
Subject: [PATCH 1/2] PR c/108150 - Fix alignment test for Windows targets
gcc/testsuite/ChangeLog:
PR c/108150
*
On 1/6/23 18:10, Jakub Jelinek wrote:
On Sat, Jan 07, 2023 at 02:01:05AM +0800, LIU Hao via Gcc-patches wrote:
libgomp/
PR middle-end/108300
* config/mingw32/proc.c: Define `WIN32_LEAN_AND_MEAN` before
.
This change is ok for trunk.
Jakub
Pushed to master b
On 12/24/22 21:22, i.nix...@autistici.org wrote:
On 2022-12-24 15:57, i.nix...@autistici.org wrote:
On 2022-12-24 15:42, i.nix...@autistici.org wrote:
fixed and tested.
Jonathan Yong, could you please apply the attached patch too?
kings regards!
oh no...
please wait.
fixed now.
bootst
On 12/22/22 12:28, i.nix...@autistici.org wrote:
On 2022-12-22 12:21, Jonathan Yong wrote:
hello,
On 12/16/22 19:20, Eric Botcazou wrote:
The libgcc parts look reasonable to me, but I can't approve them.
Maybe Jonathan Yong can approve those parts as mingw-w64 target
maintainer, or maybe a li
On 12/16/22 19:20, Eric Botcazou wrote:
The libgcc parts look reasonable to me, but I can't approve them.
Maybe Jonathan Yong can approve those parts as mingw-w64 target
maintainer, or maybe a libgcc approver can do so.
OK.
The libstdc++ parts are OK for trunk. IIUC they could go in
separatel
On 12/20/22 16:55, Andrew Pinski wrote:
On Tue, Dec 20, 2022 at 1:22 AM Jonathan Yong via Gcc-patches
wrote:
This fixes the following:
It is not obvious from the email, why this patch is needed but I
figured it was due to LLP64 targets or some other targets where long
is not the same size
This fixes the following:
Excess errors:
gcc/testsuite/gcc.c-torture/compile/pr55569.c:13:12: warning: overflow
in conversion from 'long long unsigned int' to 'long int' changes value
from '4611686018427387903' to '-1' [-Woverflow]
gcc/testsuite/gcc.c-torture/compile/pr55569.c:13:34: warning
On 10/31/22 15:22, i.nixman--- via Gcc-patches wrote:
On 2022-10-31 09:18, Eric Botcazou wrote:
Hi Eric!
thank you very much for the job!
I will try to build our (MinGW-Builds project) builds using this patch
and will report back.
@Jonathan
what the next steps to be taken to accept this pat
On 10/22/22 11:54, LIU Hao wrote:
This allows building libobjc and enabling Objective-C. Tested against
GCC 12 branch on i686-w64-mingw32.
Done, pushed to master branch.
On 10/14/22 09:39, Jonathan Yong wrote:
On 10/11/22 13:22, LIU Hao wrote:
在 2022-10-10 23:56, LIU Hao 写道:
在 2022-10-04 20:44, LIU Hao 写道:
Attached are revised patches. These are exported from trunk.
Revised further. The patch for libgfortran has been committed to
trunk today, so I include
On 10/11/22 13:22, LIU Hao wrote:
在 2022-10-10 23:56, LIU Hao 写道:
在 2022-10-04 20:44, LIU Hao 写道:
Attached are revised patches. These are exported from trunk.
Revised further. The patch for libgfortran has been committed to trunk
today, so I include only the other two.
* In the second
On 10/5/22 09:15, Torbjorn SVENSSON via Gcc-patches wrote:
Hi,
Ping, https://gcc.gnu.org/pipermail/gcc-patches/2022-September/602541.html
Kind regards,
Torbjörn
Looks good to me, pushed to master branch as
fa8e3a055a082e38aeab2561a5016b01ebfd6ebd.
On 10/5/22 09:34, Jonathan Yong wrote:
On 9/29/22 17:38, Torbjörn SVENSSON via Gcc-patches wrote:
When running the DejaGNU testsuite on a toolchain built for native
Windows, the path /dev/null can't be used to open a stream to void.
On native Windows, the resource is instead named "nul".
The er
On 9/29/22 17:38, Torbjörn SVENSSON via Gcc-patches wrote:
When running the DejaGNU testsuite on a toolchain built for native
Windows, the path /dev/null can't be used to open a stream to void.
On native Windows, the resource is instead named "nul".
The error would look like this:
c:/arm-11.3.re
On 9/8/22 11:02, Jan-Benedict Glaw wrote:
Hi!
The mingw32 port is the only port to have TARGET_OVERRIDES_FORMAT_ATTRIBUTES
defined. When this macro is defined, it will never evaluate to NULL, so this
check just leads to a warning:
/usr/lib/gcc-snapshot/bin/g++ -fcf-protection -fno-PIE -c -DIN
On 5/10/22 13:30, LIU Hao wrote:
在 2022-05-10 20:00, Xi Ruoyao 写道:
On Tue, 2022-05-10 at 19:35 +0800, LIU Hao via Gcc-patches wrote:
Subject: [PATCH] Remove size limit of PCH
Make it "Remove size limit of PCH [PR14940]", so once it's committed a
message will show up in bugzilla.
Here is t
On 9/9/21 1:19 PM, Richard Biener wrote:
The following removes the unused config/dbx.h file and removes the
setting of PREFERRED_DEBUGGING_TYPE from dbxcoff.h which is
overridden by all users (djgpp/mingw/cygwin) via either including
config/i386/djgpp.h or config/i386/cygming.h
There are still c
On 8/31/21 9:02 AM, Jonathan Wakely wrote:
It looks like my questions about this patch never got an answer, and
it never got applied.
Could somebody say whether TLS is enabled for native *-*-mingw*
builds? If it is, then we definitely need to add GCC_CHECK_TLS to the
cross-compiler config too.
On 8/25/21 11:06 PM, Jeff Law wrote:
On 8/25/2021 10:46 AM, Jonathan Yong via Gcc-patches wrote:
Attached patches OK?
cygming-crtend.c: fix build warnings
libgcc/Changelog:
* config/i386/cygming-crtend.c: Fix register_frame_ctor
and register_frame_dtor
Attached patches OK?
cygming-crtend.c: fix build warnings
libgcc/Changelog:
* config/i386/cygming-crtend.c: Fix register_frame_ctor
and register_frame_dtor warnings.
extend.texi: add note about reserved ctor/dtor priorities
gcc/Changelog:
*
On 8/23/21 1:07 AM, Jeff Law wrote:
On 8/21/2021 9:10 PM, Jonathan Yong via Gcc-patches wrote:
Attached patch OK?
2021-08-22 Jonathan Yong <10wa...@gmail.com>
gcc/testsuite/ChangLog:
* gcc.c-torture/execute/gcc_tmpnam.h: Fix tmpnam case on Windows
where it can return a fi
Attached patch OK?
2021-08-22 Jonathan Yong <10wa...@gmail.com>
gcc/testsuite/ChangLog:
* gcc.c-torture/execute/gcc_tmpnam.h: Fix tmpnam case on Windows
where it can return a filename with "\" to indicate current
directory.
* gcc.c-torture/execute/fprintf-2.c:
On 8/11/21 2:21 PM, Eric Botcazou wrote:
Hi,
as already mentioned on the list, binutils 2.36 generates PIE executables by
default on native Windows (because --dynamicbase is the default) so it makes
sense to have a simple way to counter that and -no-pie seems appropriate,
all the more so that it
On 4/9/21 11:46 AM, Martin Storsjö wrote:
This is similar to what was done in
eea4e2ff0a3f5e7f37df204c070cc5d9ef339e6e (where it was added to
STAGE*_CXXFLAGS), but this adds the flag to the CXXFLAGS and
BOOT_CXXFLAGS variables too (as it's already added to CFLAGS and
BOOT_CFLAGS).
2021-04-09 Ma
On 4/9/21 11:46 AM, Martin Storsjö wrote:
This is similar to what was done in
eea4e2ff0a3f5e7f37df204c070cc5d9ef339e6e (where it was added to
STAGE*_CXXFLAGS), but this adds the flag to the CXXFLAGS and
BOOT_CXXFLAGS variables too (as it's already added to CFLAGS and
BOOT_CFLAGS).
2021-04-09 Ma
On 11/16/20 5:40 AM, Jonathan Yong wrote:
On 11/14/20 12:29 PM, Liu Hao via Gcc-patches wrote:
This is the third revision of my patch:
1. Two typos in the commit message have been fixed.
2. Support for `%a` and `%A` has been added. Documentation can be
found on the same page in the commit m
On 11/14/20 12:29 PM, Liu Hao via Gcc-patches wrote:
This is the third revision of my patch:
1. Two typos in the commit message have been fixed.
2. Support for `%a` and `%A` has been added. Documentation can be
found on the same page in the commit message.
3. GCC will no longer warn about 'I
libgomp build fails because of the false -Wformat error, even though:
1. Correct C99 inttypes.h macros are used.
2. __mingw_* C99 wrappers are used.
3. The printf attribute is used, but it was aliased to ms_printf
The attached patch makes mingw-w64 printf attribute equivalent to other
platforms
cygwin/mingw hosted linker may support multiple targets with ELF relro
support. This breaks configure testing.
Attached patch excludes cygwin/mingw PE format from relro linker flag.
Patch OK?
From a72f02aec065c312528e41e4243c702d7371b5ce Mon Sep 17 00:00:00 2001
From: Jonathan Yong <10wa...@gma
On 11/6/20 8:34 AM, Martin Storsjö wrote:
On Fri, 6 Nov 2020, Liu Hao via Gcc-patches wrote:
在 2020/10/29 下午3:56, Liu Hao 写道:
I forward it here for comments.
Basing on the behavior of both GCC and Clang, `__cxa_thread_atexit`
is used to register the
destructor of thread_local objects directl
On 11/6/20 3:27 AM, Jeff Law wrote:
On 11/2/20 5:05 AM, Kai Tietz via Gcc-patches wrote:
Hello,
as noone seems to be able to review this patch, I will do so, even if
this is no longer a task of mine.
The patch itself is reasonable and seems to fix a pending issue we
have on CFA support. I had
On 10/20/20 2:03 AM, Jonathan Yong wrote:
On 9/16/20 1:16 PM, JonY wrote:
For platforms like Mingw and Cygwin, cygwin refuses to generate the
shared library without using -no-undefined.
Attached patch makes sure the right flags are used, since libtool is
already used to link libstdc++.
Patch O
On 9/8/20 12:21 PM, Martin Storsjö wrote:
Previously, the SEH version of _Unwind_Backtrace did unwind
the stack and call the provided callback function as intended,
but there was little the caller could do within the callback to
actually get any info about that particular level in the unwind.
Se
On 10/27/20 2:38 PM, Liu Hao via Gcc-patches wrote:
在 2020/10/8 22:56, Jason Merrill 写道:
Hmm, why isn't the mingw implementation used for all programs? That would
avoid the bug.
There was a little further discussion about this [1].
TL;DR: The mingw-w64 function is linked statically and su
On 10/22/20 11:30 AM, Alexandre Oliva wrote:
On Oct 22, 2020, Jonathan Yong wrote:
No objections for mingw-w64 since it has been tested, but I'm not
certain if the original mingw.org version has it.
Prompted by you, I looked into the original mingw32, and found it does
NOT have sincos, so I w
On 10/22/20 5:01 AM, Alexandre Oliva wrote:
Err, sorry, I mislabeled this patch as [FYI,Ada], but it is neither
about Ada nor pre-approved. It does require a review before I can check
it in.
No objections for mingw-w64 since it has been tested, but I'm not
certain if the original mingw.org v
On 9/16/20 1:16 PM, JonY wrote:
For platforms like Mingw and Cygwin, cygwin refuses to generate the
shared library without using -no-undefined.
Attached patch makes sure the right flags are used, since libtool is
already used to link libstdc++.
Patch OK?
Ping.
OpenPGP_0x713B5FE29C145D45_an
80 matches
Mail list logo
