-
Notifications
You must be signed in to change notification settings - Fork 555
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
B::CC cannot sort #1659
Comments
This simple program: for $k (sort { length $ENV{$b} <=> length $ENV{$a} } keys %ENV) {
print "$k=$ENV{$k}\n";
} Under B::Bytecode, produces correct results, then SEGVs Under B::C, produces correct results, then exits correctly. Under B::CC, produces no results, but goes into recursive --tom
|
From tchrist@chthon.perl.comThis simple program: for $k (sort { length $ENV{$b} <=> length $ENV{$a} } keys %ENV) { Under B::Bytecode, produces correct results, then SEGVs Under B::C, produces correct results, then exits correctly. Under B::CC, produces no results, but goes into recursive --tom #0 0x4015825e in tcgetattr () [the following 25000 identical stackframes deleted] |
@rspier - Status changed from 'open' to 'resolved' |
From @schwern
Now working in 5.8.6.
Still working in 5.8.6.
$ perlcc -O foo Same for bleadperl. |
From guest@guest.guest.xxxxxxxx sub B::OP::_save_common_middle { Is the actual _save_common_middle code. Unfortuantely I don't quite sub B::FAKEOP::save { I tried browsing the code to see where $op-> would at all come up |
@smpeters - Status changed from 'open' to 'stalled' |
From @rurbanTicket moved to [CPAN #53536] in the B-C queue. Please close it someone. * CC.pm (1.02_03): fixed endless loop in optimized sort. The sortcv More pp_sort bugs are handled in # 25 - simple sort # 18 - custom key sort 18 # 19 - fool the sort optimizer by my $p. This pp_sort works ok now on CC |
The RT System itself - Status changed from 'stalled' to 'open' |
@rgs - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#2900 (status was 'resolved')
Searchable as RT2900$
The text was updated successfully, but these errors were encountered: