Front page | perl.perl5.porters |
Postings from August 2016
On Tue Feb 17 15:16:50 2015, tonyc wrote: > On Tue Feb 17 06:13:36 2015, demerphq wrote: > > On 17 February 2015 at 20:39, Tony Cook via RT > > <perlbug-followup@perl.org> wrote: > > > On Tue Feb 17 03:50:55 2015, demerphq wrote: > > >> Could you please run > > >> > > >> TEST_ARGS="-v -re re\/regexp\.t" make test_harness > > >> TEST_ARGS="-v -re re\/pat_re_eval" make test_harness > > >> > > >> And send the output? > > > > > > Attached. > > > > > > If I build with -DDEBUGGING then all tests are successful, the > > > tests > > > are only failing on non-debugging builds. > > > > I see. That suggests an optimization bug in the compiler to me. Can > > you build a non-debugging build with -Og and -O1 or the equivalent > > and > > see if it also passes? > > > > Note you may speed things up by using > > > > make test-reonly > > > > to run just the regex tests. > > All tests pass with -Doptimize="-g -O1". > > That doesn't mean it's an optimization bug - we've have at least a > couple of issues where we've had apparent compiler optimization bugs > that turned out to be perl bugs. > > That said, Intel don't appear to be offering free use of their > compilers to open source developers right now[1] (I'm using an > evaluation license), so this may not be worth following up. > > Tony > > [1] https://software.intel.com/en-us/non-commercial-software- > development Is this worth following up? Does valgrind run so that it can see if perl is doing out-of-bounds accesses -- Karl Williamson --- via perlbug: queue: perl5 status: open https://rt.perl.org/Ticket/Display.html?id=123853