Displaying 2 results from an estimated 2 matches for "__clang_patchlevel__".
2016 Jun 28
0
[lldb-dev] [cfe-dev] [Openmp-dev] What version comes after 3.9? (Was: [3.9 Release] Release plan and call for testers)
...doing 5.0 next, users will
get confused when we ship 4.1 as a "dot" release instead of a major
release like we've used to.
There's also the question of how to practically go from a 3-tuple to a
2-tuple. Should we drop it from the version string and dir names in
Clang? Do we drop __clang_patchlevel__ or just leave it at zero? I see
GCC 5.4 is actually versioned as 5.4.0 so maybe that'd be the way to
do it?
Cheers,
Hans
2016 Jun 28
5
[cfe-dev] [Openmp-dev] [lldb-dev] What version comes after 3.9? (Was: [3.9 Release] Release plan and call for testers)
On Tue, Jun 28, 2016 at 12:55 PM, Chandler Carruth via cfe-dev <
cfe-dev at lists.llvm.org> wrote:
> On Tue, Jun 28, 2016 at 12:45 PM Rafael Espíndola <
> openmp-dev at lists.llvm.org> wrote:
>
>> > I don't think this is as obvious as you might think it is. We can
>> happily
>> > drop the "major version equals bitcode compatibility"