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
Weird error building rakudo #930
Comments
From paco.linux@gmail.comHi: I'm having a very weird error while building latest rakudo with parrot cc -c -o perl6_ops_cg.o -I/tmp/rakudo/parrot/include In /parrot/languages/rakudo/src/ops/perl6.ops there is this comment : 73 /* Using memcpy here may trigger gcc optimizations, which at I have tried in other machines and have no problem, so I think is a problem paco@javier:/tmp/rakudo$ gcc --version The problem went away using other switches while compiling rakudo (using All tests successful. /rakudo/parrot$ cat myconfig Paco -- |
From @jeffhorwitzI've reproduced this problem on my machine (CentOS 5, x86 VMware ESX, Building Rakudo with ICU enabled on x86 (gcc 4.1.2) results in the perl6.ops: In function cg_perl6: ========== This output is similar to the memcpy issue I patched in the same file 135 inline op is_uprop(out INT, in STR, in STR, in INT) :base_core { There is likely some compiler optimization going on in that block that |
The RT System itself - Status changed from 'new' to 'open' |
From he@uninett.noOn Tir. 21. Apr. 2009 07:41:21, PacoLinux wrote:
I'm seeing the same problem with gcc version 4.1.2 20061021 prerelease In my case, I found out that what caused the error was not optimization, perl ./Configure.pl --gen-parrot --gen-parrot-option=--optimize in the rakudo root directory. That way, the relevant file gets compiled Yes, this is actually a gcc bug... Hope this helps, - Håvard |
From @jnthnOn Sun May 17 12:16:57 2009, heidnes wrote:
Yup, and there's no obvious workaround we can do in the code. So, going Thanks, Jonathan |
@jnthn - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#64930 (status was 'resolved')
Searchable as RT64930$
The text was updated successfully, but these errors were encountered: