(upstream bug is https://code.google.com/p/chromium/issues/detail?id=124610)

Renato, maybe you know if anyone cares about this?

Hi Nico,

I'm interested in IAS bugs, as well as some other folks like Saleem and ARM, but I can't pursue the Chromium project myself. I hadn't seen the attached bugs to this one, but I will now.

As a general rule, pre-UAL support as well as GNU extensions have less priority and might not even be implemented, with the rule of thumb being about the complexity of the patch needed to enable support. If it's just an alias or a simple match, it should be ok, but if it needs substantial support from the assembler just for that legacy/extension, than it's likely not going in.

I'll review each one of the depending bugs individually, thanks for getting my attention to this.

cheers,
--renato

I hadn't seen the attached bugs to this one, but I will now.

Cool. It's probably not a complete list; I'll add more things over time.

pre-UAL support

What's "UAL"?

as well as GNU extensions

Is there a standard for assemblers? I thought it's all implementation-defined. How do I know if something is a GNU extension? (The two patches I've sent so far fall into the "low complexity" bucket though, I think.)

pre-UAL support

What's "UAL"?

Unified assembly language. The ARM assembly evolved over time, and had lots of different mnemonics that behaved slightly differently. In order to simplify things, the FPU and CPU operations were renamed and made uniform and became known as UAL.

GAS doesn't default to it, though it supports it. Just make sure that you add

.syntax unified

to the beginning of any assembly file and things should be completely compatible against any reasonably recent version of binutils and LLVM IAS.

Hi Saleem,

Thanks for answering the question, I completely missed that.

Nico, about the standards for ASM, unfortunately there isn't. UAL is an attempt from ARM to create a unified assembly syntax, but there are probably as many extensions from GNU, ARM and LLVM together than there are rules. The UAL not only unified ARM and Thumb, but also deprecated some old mnemonics.

http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0473c/BABJIHGJ.html

Most of the problems we have now on the integrated ARM assembler are due to pre-UAL and extensions syntax being used in the wild, and we have to balance implementing them or kindly requesting the users to update their syntax. The rules of thumb are:

• Non-extensions/non-pre-UAL issues are critical, needs fixing in the integrated assembler.

• Extensions/pre-UAL can be fixed in the assembler if:

• The syntax is an alias/mnemonic to a UAL token and implementing it would just mean adding a new case to a switch or similar.
• The syntax is widely used in the wild and asking all users would be impractical. In this case, a discussion should be held as to what's the best way to implement without making the whole code worse. We might decide we can't.

• Changes that require deep changes to the compiler, or are easily worked around by another feature, or would make it harder to maintain other areas of the compiler should NOT go in.

Current status: -integrated-as is enabled for all but four targets (https://bugs.chromium.org/p/chromium/issues/detail?id=124610#c33)

mentioned in issue #20800

mentioned in issue #20797

mentioned in issue #20802

mentioned in issue #20803

mentioned in issue #20801

mentioned in issue #20821

mentioned in issue #21074

mentioned in issue #21076

mentioned in issue #21794

mentioned in issue #23374

mentioned in issue #26096

mentioned in issue #26094

mentioned in issue #30406

This has been fixed for a while. https://crbug.com/124610 was the last holdout, and it got resolved 4 years ago or so.