Front page | perl.perl5.porters |
Postings from June 2019
AFAIK, although we know how to trigger it, we haven't yet identified the bug - and therefore we are still unable to report it. I did spend some time a while back trying to create a C script that would demo the issue, but failed miserably. Using the mingw64 port of gcc-8.3.0 that ships with StrawberryPerl-5.30.0, I find it's also exhibiting the bug - just like the 8.1.0 and 8.2.1 mingw64 compilers that I had tried earlier. Cheers, Rob On Fri, May 31, 2019 at 10:43 PM James E Keenan via RT < perlbug-followup@perl.org> wrote: > On Wed, 24 Apr 2019 11:32:38 GMT, davem wrote: > > On Tue, Apr 23, 2019 at 11:03:35PM +0200, Tomasz Konojacki wrote: > > > Dave Mitchell <davem@iabyn.com> wrote: > > > > > > > I think perhaps for 5.30.0 we should revert the entirely of the > > > > "HAS_BUILTIN_EXPECT on MinGW" patch, then move this ticket from the > > > > 5.30.0 > > > > to the 5.32.0 blockers list and return to the issue after 5.30.0 is > > > > released. > > > > > > Yeah, I think it's the best course of action. I hoped we would find > > > the > > > cause and report it to gcc/binutils/mingw-w64/whatever-is-at-fault so > > > they could fix it in time for 5.30 release, but unfortunately that > > > didn't happen. > > > > Now reverted with v5.29.10-13-gabd494f123. I'll move it to the 5.32.0 > > blockers list. > > Have we identified the cause of the problem reported in this ticket (such > that we can report the bug externally)? > > Thank you very much. > > > -- > James E Keenan (jkeenan@cpan.org) > > --- > via perlbug: queue: perl5 status: open > https://rt.perl.org/Ticket/Display.html?id=133603 >Thread Previous | Thread Next