User Details
- User Since
- Dec 1 2019, 10:01 AM (72 w, 4 h)
Thu, Apr 15
Ping!! :)
Wed, Apr 14
- Addressed comments (removed superfluous test, added a possible missing test)
Tue, Apr 13
- Rebase on latest master x2 (since the macho tests seem to be fixed)
- Rebasing on latest master to account for the motorola integer changes that was merged recently
- Rebase on latest master
- Rebase on latest master
- Updating repo to rg Github monorepo (no functional changes)
Mon, Apr 12
Ping :)
Fri, Apr 9
Thu, Apr 8
Are there any other review comments on this patch before I merge it in? Thanks!
Wed, Apr 7
Changes LGTM. I'm assuming there's no additional dependencies for this patch?
Tue, Apr 6
- Applying same patch again.
- Addressed Comments (Rename of MCAsmInfo attribute)
Hi All!
Does anyone have feedback on the patch / approach taken? Any opinions would be greatly welcome and appreciated! :)
Mon, Apr 5
It looks like this adds support for X86 identifiers starting with $ (I'm actually surprised this wasn't allowed before).
- Rebasing on latest master + setting the AllowHashInIdentifier in HLASMAsmParser since it has landed.
- Appeasing clang-tidy (rename of variable from camelCase to CamelCase)
- Addressed Comments
- Moved logic for LexHLASMIntegers to the main block where decimal integers are parsed.
- Addressed Comments
- Renamed MCAsmInfo attribute with a more positive meaning
- Updated tests and AsmLexer with new attribute name.
This does not necessarily mean a conflict. As an concrete example, ld.lld treats # as an additional comment marker for linker scripts. GNU ld don't do this.
The ld.lld way can be seen as an extension. Since there is no meaningful syntax starting with # in GNU ld linker scripts, reserving # for an additional comment marker is totally fine.
My question here is similar. If there is no meaningful syntax starting with /* or //, we don't necessarily detect such cases.
Sun, Apr 4
Sat, Apr 3
Fri, Apr 2
Thu, Apr 1
- Rebase on latest master
- Rebasing on latest master.
Wed, Mar 31
Ping :)
The only difference should be in the actual assembly syntax itself, however, you raise an interesting point because in Motorola-flavour assembly %0/%1 would be parsed as a single-bit constant... Which I hadn't thought of.
I'll be honest: at this stage I've not tested inline assembly at all.
Ping :) :)
- Addressed Comments x2 (Reordered the check in isIdentifierChar)
Tue, Mar 30
I came across the series of patches that are adding Motorola asm support. I have a quick question as I'm not too familiar with Motorola asm.
Mon, Mar 29
Gentle Ping :)
- Rebasing on latest master
- Addressed comments (Minor formatting changes)
Thu, Mar 25
Ping Ping! :) :)
Wed, Mar 24
- Few formatting changes + making the unittest a bit more robust in the tokens it was checking
- Addressed clang-tidy warnings/errors
- Addressing Comments (Changing comment with the updated grammar)
Mon, Mar 22
LGTM