Closed Quuxplusone closed 13 years ago
Bugzilla Link | PR4696 |
Status | RESOLVED LATER |
Importance | P normal |
Reported by | Edward O'Callaghan (eocallaghan@alterapraxis.com) |
Reported on | 2009-08-06 20:33:10 -0700 |
Last modified on | 2011-02-09 01:11:58 -0800 |
Version | trunk |
Hardware | PC AuroraUX |
CC | llvm-bugs@lists.llvm.org |
Fixed by commit(s) | |
Attachments | |
Blocks | |
Blocked by | PR3679, PR5326, PR4672, PR4690, PR4695, PR4697, PR5172, PR5307 |
See also |
I have to say, I'm a little ambivalent about us having these bugs in our repository. It just means we get more mail about bugs, I'm not sure it actually helps clang development any.
Well for one, I can't add all my bug reports to the freebsd tracker (although
we have had a fair amount of overlap until recently, so I had been holding off).
AuroraUX is a very large scale project, much like freebsd that explores
'interesting' corners of compilers and I need a method to track all our issues
with clang building the AuroraUX/OpenSolaris kernel.
Further to this, I am pretty much maintaining the Solaris and AuroraUX port of
all the compiler infrastructure solo as far as I can tell.
Also considering how new clang is and for the sack of organization and
productivity, I believe both the freebsd and this one are completely in there
right to hold such a tracker.
The freebsd one has helped crush many many bugs in both llvm and clang and I
hope we can continue this as well. However, we have a smaller team and need to
make use of good organization methods to keep things flowing in the correct
direction and make good use of time management.
Thus, I believe the above holds ample reason for this to be held and just
because we are a smaller team / less popular then the freebsd lads does not
take away our worthwhileness !
Regards,
Edward O'Callaghan.
My comment extended to the FreeBSD and Linux versions of this bug. :)
I don't see why interested teams can't track clang in their own manner. All these bugs do (for me) is mean I get 2 copies of every bug report; I generally read every bug report regardless, so, again IMHO, it doesn't actually help get things fixed.
Per the comments in this bug, there is no reason to have a meta bug here. This has also dropped out of use..