[llvm-dev] Fwd: Bugzilla OrcJIT Tickets

Stefan Gränitz via llvm-dev
2019-05-18T16:03:32Z

In fact, this is all very good practice in my opinion:
https://bugs.llvm.org/show_bug.cgi?id=30896
https://bugs.llvm.org/show_bug.cgi?id=22608
https://bugs.llvm.org/show_bug.cgi?id=24159

Back in 2016 I simply didn't know about the Bugzilla tracker.
From today's perspective, I think, we should try and revive this spirit
and share rough plans there.

@Praveen very good initiative!
https://bugs.llvm.org/show_bug.cgi?id=41075

@Machiel: This is quite recent, but didn't land after it was accepted.
Objections?
https://reviews.llvm.org/D61599

Cheers

-------- Forwarded Message --------
Subject: 	Bugzilla OrcJIT Tickets
Date: 	Sat, 18 May 2019 17:47:58 +0200
From: 	Stefan Gränitz <stefan.graenitz at gmail.com>
To: 	via llvm-dev <llvm-dev at lists.llvm.org>



Hello everyone

A previous thread about OrcJIT brought up bug reports on Bugzilla. A
quick search gives 20+ results:
https://bugs.llvm.org/buglist.cgi?component=OrcJIT&list_id=162232&query_format=advanced&resolution=---

While some of them are obviously outdated (addModuleSet API cleanup
[1]), others may actually be relevant again (Small code model? [2]). If
you reported one of them, please take the time (some day) and review
from today's perspective.

Are there recommendations regarding Bugzilla reports from other parts of
LLVM? Best practices that worked out well?

Thanks!
Stefan

--

[1] https://bugs.llvm.org/show_bug.cgi?id=30896
[2] https://bugs.llvm.org/show_bug.cgi?id=24159

--
https://flowcrypt.com/pub/stefan.graenitz at gmail.com



-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20190518/416611b7/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20190518/416611b7/attachment.sig>