Mail Archives: cygwin/2014/07/17/14:25:06
--4eRLI4hEmsdu6Npr
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Jul 17 16:31, Jon TURNEY wrote:
> On 17/07/2014 08:37, Corinna Vinschen wrote:
> >On Jul 17 06:02, JonY wrote:
> >>On 7/16/2014 15:02, Corinna Vinschen wrote:
> >>>On Jul 15 16:39, Corinna Vinschen wrote:
> >>>>On Jul 15 21:55, JonY wrote:
> >>>>>On 7/15/2014 21:08, Corinna Vinschen wrote:
> >>>>>>>
> >>>>>>>FWIW, the problem disappears if I revert gcc-core and libgcc1 to 4=
.8.2-2.
> >>>>>>
> >>>>>>JonY, do you have a chance to have a look into this issue?
> >>>>>
> >>>>>Sorry, I have been busy these few weeks, but I am well aware that th=
ere
> >>>>>is a problem with one of the libgcc changes, but has yet to investig=
ate it.
> >>>>>
> >>>>>I believe Jon Turney has looked into it somewhat.
>=20
> I think this is the same or a similar problem to the one I reported at [1=
].
> I also created a gcc bug [2], with a suggested patch.
>=20
> >>>>Sounds good. Thanks in advance.
> >>>
> >>>Yesterday I asked my collegues to take a stab at the issue and one of
> >>>them, DJ Delorie, came up with a libgcc patch already. It hasn't been
> >>>sent upstream yet. Can we give it a try, perhaps by creating a new
> >>>libgcc DLL, please?
> >>
> >>Thanks, I'll get to it this weekend, should I make the new gcc an
> >>experimental version? Or is just the libgcc binary required?
> >
> >It's the libgcc DLL which gives us grief, so a new libgcc package is
> >sufficent, afaics. We should check if this DLL fixes the problem and
> >then make it "curr" soon, I think.
>=20
> I briefly tested this other patch with my test case from the mail above, =
and
> it doesn't seem to help.
>=20
> On 15/07/2014 15:45, Jan Nijtmans wrote:
> > Is this essentially the same problem as described here?
> >
> > <http://gcc.gnu.org/ml/gcc/2013-05/msg00180.html>
>=20
> No, I think it is an unforeseen consequence of the patch [3] to fix that =
bug
> [4], which I believe is present in 4.8.3-1, introducing a new problem when
> an executable which doesn't depend on libgcc dlopen()s a dll which does.
>=20
> [1] https://cygwin.com/ml/cygwin/2014-07/msg00083.html
> [2] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D61752
> [3] https://sourceware.org/ml/cygwin/2013-07/msg00528.html
> [4] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D57982
I asked DJ to take another look, but I guess ultimately we need the
attention of one of the GCC Windows maintainers. Kai Tietz seems to be
unavailable right now, unfortunately.
Corinna
--=20
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
--4eRLI4hEmsdu6Npr
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBAgAGBQJTyBTcAAoJEPU2Bp2uRE+gYdgP/iwizCfwmxNFrLNGcLzL60n0
fIVvut2YZFVtXik1bpFJngtDXypdwn2rl9fkC/xVeciZzi/ZRcIsv/m/n7mVJ24A
60a45OpT1SVPbZXveTx3Awlv9RCXM/bjfiesaEB/UgPq8gfvKVTJ8mL3X6hWMF4v
J8qb0Go+db+DzmbHBizLy0bEQeOfF4Fy7Rhy35LaXq+gHu0RUTxG957VeEjj+ltM
snXqQkJTzmL1MnMZY8FkdcNW7IQycbF9unLOlN5IQPMsYA/nWD3SLrFssy+WZbJK
ZBWQCKmzD+vKpnTW1tAFIj8bP3I2gblSZJ1cWYBdKERVKE8EtKS5GxgZgs1Sx505
2j1mqQBiBkpgR0yE4MpEjzEaMKLNTmJX0qT6CXSJKSjnVOOaqqsViqtvzqNZLaPh
yhwYTPjcavYOQnrS+zSh+LmRtw6R83AQmR22UgkpbmzCjAU20fJMqZHniqDJWcTC
pvIdU+WoTPXwid7jLNVM4W0rmpXjWtd8IUxu/c9e6Zz6/73Ug8CAkniPAAq+/7wj
ovZOjOnWFg8Mq1JpD+PzA1isAY8c4lpm8aQuM2Zld8jn7WYtZMy9okn5WMURuOmi
uXIMwLbLxDwpUiXOp6GzwVFQE1y8aWxBsaiVRQMTOJNFfmLDqxf+Bqr2MZVVNC8m
dEE0jX4PO4puZhW4CGPb
=mX2Z
-----END PGP SIGNATURE-----
--4eRLI4hEmsdu6Npr--
- Raw text -