[cfe-dev] Clang fails to compile the mix of intel/att assembly, and as a result BitcoinArmory — the major bitcoin client — also doesn't build

[Reid Kleckner]

On Mon, Mar 30, 2015 at 12:27 PM, Yuri <yuri at rawbw.com> wrote:

> On 03/30/2015 11:56, Reid Kleckner wrote:
>
>>
>> The problem is that the directives are lexing the semicolon character
>> when it's supposed to be a statement separator.
>>
>> It should be both easy to work around in the source and easy to fix in
>> LLVM. Given the easy source workaround, this doesn't feel very high
>> priority.
>>
>
> This bug report maybe boils down to statement separator, but Armory
> problems are wider. Even after separator is replaced, compile still breaks
> in clang due to other clang vs. gcc differences.


That is to be expected. There are limits to how far we can go for gcc
compatibility, and we have to strike a practical balance somewhere.

If you can investigate the specific issues and file bugs on the ones not
already in the tracker, we can better assess if it's worth changing Clang.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20150330/4749a1ad/attachment.html>