https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241848
--- Comment #10 from Mark Millard <marklmi26-f...@yahoo.com> --- (In reply to Robert Clausecker from comment #9) > I am extremely sure this is a compiler bug or poorly designed program You may or may not be right. I do not have the knowledge to know what is appropriate to expect for the test case. I do not know what reasonable memory use figures would be. I do not know which side of that "or" should have the blaim (or if either should). I've no clue just what would need to change in either (if anything). > Please solve the underlying issue. I want a solution, not a bandaid. I am not a llvm developer, nor a Google Test developer. (I've only done a few small patches for FreeBSD, generally for personal use. So, effectively, I'm not a FreeBSD developer either: a user.) llvm is an upstream project used by FreeBSD but not developed by FreeBSD. There is a: https://bugs.llvm.org/ That would be a more appropriate place for requesting a fix or redesign from the compiler side of things. If they improved things, FreeBSD would pick up the change at some point. Google Test is an upstream project used by FreeBSD but not developed by FreeBSD. It looks like it uses: https://github.com/google/googletest/issues for submitting and tracking issues. That would be a more appropriate place for requesting a fix or redesign from the Google Test side of things. I've no evidence for which place would be the right place to submit something. I do know that FreeBSD's bugvilla is not the right place for upstream project changes. (Although having a FreeBSD bugzilla item for pointing to an upstream item for reference can be appropriate at times.) -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
