https://llvm.org/bugs/show_bug.cgi?id=21435
Jose Fonseca <jfons...@vmware.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |---
--- Comment #16 from Jose Fonseca <jfons...@vmware.com> ---
(In reply to comment #15)
> This is over a year old and the attached LLVM IR no longer parses with TOT
> llc.
>
> llc's command line interface isn't exactly stable or user facing either, so
> I don't think there's anything to do here.
This bug is not specific llc...
I provided the llc command line / IR merely to _facilitate_ reproing and fixing
the bug.
We saw the bug on Mesa + llvmpipe with JIT.
The problem here is that
LLVM is broken when incoming stack aligment is 4. You can probably repro the
isse with `clang -mstack-alignment=4` and the right input.
That said, it's clear that nothing happened. So probably nothing will ever
happen. On Mac and Linux the ABI (both 32 and 64bits) states that stack
alignment is always aligned 16bytes, so this is never a issue. (Maybe it
matters for Microsoft, since on Windows 32 bits, the stack alignment is
4bytes.)
But, if you don't want to fix, then at very least mark it as WONTFIX. Closing
as INVALID on the grounds you can't no longer repro is IMO insult to the time I
spent on obtaining a small repro, as per the bug guidelines.
LLVM has very little stable interfaces, so if LLVM devs sleep it long enough
you can close any bug on the basis you can repro...
--
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
