On Tue, 08 Nov 2016 01:48:18 GMT, dcollinsn@gmail.com wrote: > Greetings. The above commit seems to break XS::TCC v0.04, due to the > following errors: > > tcc: error: undefined symbol '__builtin_expect' at t/10_lowlevel.t line 82. > tcc: error: undefined symbol '__builtin_expect' at t/30_inline.t line 24. > > Bisect: > > cpanbisect@digitalis:~/perl$ perl Porting/bisect.pl --module=XS::TCC > --start=11a12be --end=fe546b3 -Dusedevel -DDEBUGGING -Dusethreads > ... > <SNIP> > ... > 36195052d1d557ad70ddca695d75e18cb1fc3bbb is the first bad commit > commit 36195052d1d557ad70ddca695d75e18cb1fc3bbb > Author: Karl Williamson <khw@cpan.org> > Date: Tue Oct 25 10:47:23 2016 -0600 > > Add branch predictors for DEBUG statements > > It is unlikely that any given debug flag will be set in any given run, > even under DEBUGGING builds. > > :100644 100644 b43ae90e1282fa980c9f15d39bddd3ecc6a22e8c > accc628c3b76cc392ad4cdbfbc3a9f50fdce98d0 M perl.h > bisect run success > That took 3342 seconds. > > Perl -V included in the attached CPAN Testers reports (which are not > uploaded yet, since I'm still working through this run.) > > -- > Dan What is puzzling about these failures is that *most* of the smoke testing runs on this platform after the commit indicated via bisection have gotten PASS. See: http://matrix.cpantesters.org/?dist=XS-TCC;os=linux;perl=5.25.7;reports=1#sl=1,1 On the other hand, configuring in a way very similar to the way Dan Collins did in http://www.cpantesters.org/cpan/report/c08895d8-a65f-11e6-932a-f4415c96acb4 (now, a month-and-a-half ago), I was able to reproduce the same test failures. The documentation for XS-TCC states: "This is a highly experimental module. Use at your own risk. Get in touch with the author(s) if in doubt." So perhaps that's what we have to do here. Thank you very much. -- James E Keenan (jkeenan@cpan.org) --- via perlbug: queue: perl5 status: new https://rt.perl.org/Ticket/Display.html?id=130046Thread Previous