https://bugs.llvm.org/show_bug.cgi?id=34950

Reid Kleckner <r...@google.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |DUPLICATE

--- Comment #3 from Reid Kleckner <r...@google.com> ---
(In reply to Mike Benfield from comment #0)
> Note that this is presumably caused by the same underlying problem as Bug
> 33664, which I reported earlier. I decided to report this new bug with a
> different manifestation of the problem, because the other bug report got no
> attention, despite apparently being critical to the basic usability of the
> assembler.

Unfortunately there are very few volunteers that triage the bug backlog and
posting new comments to old bugs does not send email to llvm-bugs@. This means
LLVM is often unintentionally deaf to old longstanding issues unless duplicates
are reported, which is more or less what you're doing and perfectly reasonable
given the existing limitations of our bug tracker and triage process.

Anyway, this should be fixed with r315953, and I'm going to mark it duplicated
for tracking purposes. Thanks for re-filing!

> (Speaking of which... someone else somewhere is actually using
> clang's assembler, right? It seems odd that a bug like this, one which
> surely anyone using the software would notice and be frustrated by, could
> persist for so long.)

I agree, LLVM's assembler isn't very usable. It was built to eliminate LLVM's
dependency on external assemblers, and not to be used by humans. =(

*** This bug has been marked as a duplicate of bug 33664 ***

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

Reply via email to