search for: r210062

...gain (see thread on llvmdev), but the restrictions inherent > from what alias are at the object level will remain, just be reworded > a bit. For example, we will have something along the lines of "the > aliasee expression cannot contain an undefined GlobalValue". And this is in: r210062. Let us know how it looks from GHC's point of view. Cheers, Rafael

...ctions inherent >> > from what alias are at the object level will remain, just be reworded >> > a bit. For example, we will have something along the lines of "the >> > aliasee expression cannot contain an undefined GlobalValue". >> >> And this is in: r210062. >> >> Let us know how it looks from GHC's point of view. > > > I think we might be able to relax our restrictions against aliases > referring to declarations if the alias is private. If the alias is > private, then the label never appears in the object file. The al...

Peter: Please feel free to correct me if there are any inaccuracies below. For a while now LLVM has started rejecting aliases referring to things other than definitions[1]. This unfortunately breaks GHC's LLVM code generator which referes to most symbols through aliases. This is done in two situations, 1. As place-holders for external symbols. As the code generator does not