# Bugs, restrictions, todo for dload

A small memory leak due to a bug in bfd (v2.6):
cf FIXME in archive.c:710

Doesn't support constructors nor sets.
Very unlikely to support them one day since
the sections of the same name are not allocated in one block

On Alpha, a bug in overflow chechings in bfd leads to incorrect
overflow warnings. I fixed it in the hope it willl not break 
something else ... (see bfd-2.6.patch)

On Alpha, some very large object file leads to an isolated IGNORE 
relocation which triggers an abort in bfd ???

# On Linux, libbfd.a:cache.o contains a common definition (bfd_last_cache)
# which leads to a multiple common error (bug in dlink_info_add-bfd ???)
# I couldn't yet reproduce the problem.
# Ok, Corrected 01/24/96

When the main bigloo application contains an eval or repl,
initializing a dynamic unit which is also statically linked
replaces (for the interpreter) the references to this unit's
variables with the dynamic-linked unit ones. Actually it's 
more a problem with bigloo's eval and repl ( Hopefully, when
Ramses is completely finished, the problem will be solved :))

Dynamic symbols are not supported. On systems which provide dynamic
libraries, you should link your main executable statically.