[LLVMdev] how to build eglibc using llvm-gcc without unsupported -fno-toplevel-reorder

[Sergey Yakoushkin]

Hi,

>> Are there any other issues?
> Take a look at gcc's implementation. They need to keep the order of
> every definition they see. It also has other issues:
> 1656    ... This implements -fno-toplevel-reorder. In
> 1657    this mode we may output functions and variables which don't really
> 1658    need to be output. */

Ok, option support requires to keep order of definitions and for some
reason that is undesirable in LLVM.
Then, it would be helpful to get at least some diagnostic message from
llvm-gcc on unsupported option.

Regards,
Sergey Y.