If you look at the 3 lines above the assert that is failing, you'll see
this:
// FIXME: This code should handle a couple of common cases efficiently, but
// it should also implement the general case by code-gening a new anonymous
// nullary function to call.
Basically it's saying that we only support one argument functions that
take an integer right now. This is a bug/suboptimality, hence the
FIXME.
Reid wrote:
ick! Is there a bugzilla on this?
... and filed PR419.
Since then I've implemented the FIXME, so now the JIT can call arbitrary
non-varargs functions with the runFunction method now, and I've closed
PR419.
Also, I simplified the HowToUseJIT example (which is great btw Valery,
thanks!), and changed it to print out the module it's about to execute
(better for demo purposes). I also switched to to default to using the
JIT instead of forcing the interpreter.
If you have any more problems with this, please let me know!
rsync -az --delete --exclude='#*' --stats --bwlimit=256 rsync://llvm.cs.uiuc.edu/LLVM/ /home/llvm/cvs
rsync: failed to connect to llvm.cs.uiuc.edu: Connection refused
rsync error: error in socket IO (code 10) at clientserver.c(83)
John, can you please look into this? Most likely the xinetd needs to be
restarted.I'm not sure when it started failing, but its been a while
because there have been other complaints about the mirror not being up
to date (i.e. someone checked out from it and the result wouldn't
build).
Perhaps rsyncd is not being run by xinetd? Can you see if its started?
Check to see if there is a /etc/init.d/rsyncd file. If there is, and its
not already running, try:
/etc/init.d/rsyncd start
otherwise:
/etc/init.d/rsyncd restart
Also, could you run "/sbin/chkconfig --list" and make sure the settings
for rsyncd are "on" for each of init levels 2,3,4, and 5?
Other possibilities:
firewall rule changes on zion? Is port 873 open?
firewall rule changes on uiuc net? Is port 873 open to zion?
Perhaps rsyncd is not being run by xinetd? Can you see if its started?
Check to see if there is a /etc/init.d/rsyncd file. If there is, and its
not already running, try:
/etc/init.d/rsyncd start
otherwise:
/etc/init.d/rsyncd restart
It's up now.
Also, could you run "/sbin/chkconfig --list" and make sure the settings
for rsyncd are "on" for each of init levels 2,3,4, and 5?