Why do you keep releasing new versions without fixing regressions?

Clang-6 has these 2 regressions:

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

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

You didn't fix them, and still released clang-7.

Yuri

From: cfe-dev [mailto:cfe-dev-bounces@lists.llvm.org] On Behalf Of Yuri
via cfe-dev
Sent: Tuesday, November 20, 2018 1:05 PM
To: cfe-dev@lists.llvm.org
Subject: [cfe-dev] Why do you keep releasing new versions without fixing
regressions?

Clang-6 has these 2 regressions:

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

Someone looked at this, could not reproduce it.
You reported that "clang++ 7.3.0 from the port doesn't" have it.
That makes it sound like 7.0 *did* fix the bug. If it is still
a bug, please provide details. If "the port" has a fix, please
send it back upstream so we don't have to duplicate the work.

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

Using a builtin directly in user code is asking for trouble.
Details of their calling sequences, and even whether they exist
at all, is not guaranteed from one release to the next. Use
an intrinsic or a math function here instead.

Hope this helps.
--paulr

Clang-6 has these 2 regressions:

This is a bugfix rather than a regression. Clang <=5 was miscompiling your testcase due to broken behavior of a GNU extension.

As Paul mentioned, this diagnostic is correct; the only thing you’re allowed to do with builtin functions is make direct calls to them. Sorry the diagnostic message doesn’t explain that.