thr3ads.net - llvm dev - [llvm-dev] [Release-testers] [7.0.0 Release] rc1 has been tagged [Aug 2018]

If this information is useful, please help other people find it:
Share via:

Hans Wennborg via llvm-dev

2018-Aug-03 11:37 UTC

[llvm-dev] [7.0.0 Release] rc1 has been tagged

Dear testers,

7.0.0-rc1 was just tagged (from the branch at r338847).

It's early in the release process, but I'd like to find out what the
status is of the branch on our various platforms.

Please run the test script, share the results, and upload binaries.

Thanks,
Hans

via llvm-dev

2018-Aug-03 13:38 UTC

head link

[llvm-dev] [cfe-dev] [7.0.0 Release] rc1 has been tagged

Hi Hans,

I was just trying to push a release note about DWARF v5 support. I did:
  git checkout release_70 # in the monorepo
  git commit <update to llvm/docs/ReleaseNotes.rst>
  git llvm push
but that fails.  How do you want to do release notes?

Thanks,
--paulr
> -----Original Message-----
> From: cfe-dev [mailto:cfe-dev-bounces at lists.llvm.org] On Behalf Of Hans
> Wennborg via cfe-dev
> Sent: Friday, August 03, 2018 7:38 AM
> To: Release-testers
> Cc: llvm-dev; cfe-dev; openmp-dev (openmp-dev at lists.llvm.org); LLDB Dev
> Subject: [cfe-dev] [7.0.0 Release] rc1 has been tagged
> 
> Dear testers,
> 
> 7.0.0-rc1 was just tagged (from the branch at r338847).
> 
> It's early in the release process, but I'd like to find out what
the
> status is of the branch on our various platforms.
> 
> Please run the test script, share the results, and upload binaries.
> 
> Thanks,
> Hans
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev

Hans Wennborg via llvm-dev

2018-Aug-03 13:40 UTC

head link

[llvm-dev] [cfe-dev] [7.0.0 Release] rc1 has been tagged

On Fri, Aug 3, 2018 at 3:38 PM,  <paul.robinson at sony.com>
wrote:> Hi Hans,
>
> I was just trying to push a release note about DWARF v5 support. I did:
>   git checkout release_70 # in the monorepo
>   git commit <update to llvm/docs/ReleaseNotes.rst>
>   git llvm push
> but that fails.  How do you want to do release notes?
I'm not familiar with "git llvm", but I suspect it doesn't
work for
release branches. Can you just svn commit it instead?

Thanks,
Hans
>> -----Original Message-----
>> From: cfe-dev [mailto:cfe-dev-bounces at lists.llvm.org] On Behalf Of
Hans
>> Wennborg via cfe-dev
>> Sent: Friday, August 03, 2018 7:38 AM
>> To: Release-testers
>> Cc: llvm-dev; cfe-dev; openmp-dev (openmp-dev at lists.llvm.org); LLDB
Dev
>> Subject: [cfe-dev] [7.0.0 Release] rc1 has been tagged
>>
>> Dear testers,
>>
>> 7.0.0-rc1 was just tagged (from the branch at r338847).
>>
>> It's early in the release process, but I'd like to find out
what the
>> status is of the branch on our various platforms.
>>
>> Please run the test script, share the results, and upload binaries.
>>
>> Thanks,
>> Hans
>> _______________________________________________
>> cfe-dev mailing list
>> cfe-dev at lists.llvm.org
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev

Andrew Kelley via llvm-dev

2018-Aug-05 06:42 UTC

head link

[llvm-dev] [7.0.0 Release] rc1 has been tagged

All Zig tests passed with a debug build of LLVM/Clang/LLD 7.0.0rc1.

On Fri, Aug 3, 2018 at 7:38 AM Hans Wennborg via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> Dear testers,
>
> 7.0.0-rc1 was just tagged (from the branch at r338847).
>
> It's early in the release process, but I'd like to find out what
the
> status is of the branch on our various platforms.
>
> Please run the test script, share the results, and upload binaries.
>
> Thanks,
> Hans
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20180805/53c6b77d/attachment.html>

Dimitry Andric via llvm-dev

2018-Aug-05 15:49 UTC

head link

[llvm-dev] [Release-testers] [7.0.0 Release] rc1 has been tagged

On 3 Aug 2018, at 13:37, Hans Wennborg via Release-testers <release-testers
at lists.llvm.org> wrote:> 
> 7.0.0-rc1 was just tagged (from the branch at r338847).
> 
> It's early in the release process, but I'd like to find out what
the
> status is of the branch on our various platforms.
> 
> Please run the test script, share the results, and upload binaries.
Hmm, I'm running into a rather nasty snag now on i386-freebsd11, due to our
lack of atomic 64 bit primitives; Phase2's configure dies with:

    -- Performing Test HAVE_CXX_ATOMICS_WITHOUT_LIB
    -- Performing Test HAVE_CXX_ATOMICS_WITHOUT_LIB - Success
    -- Performing Test HAVE_CXX_ATOMICS64_WITHOUT_LIB
    -- Performing Test HAVE_CXX_ATOMICS64_WITHOUT_LIB - Failed
    -- Looking for __atomic_load_8 in atomic
    -- Looking for __atomic_load_8 in atomic - not found
    CMake Error at cmake/modules/CheckAtomic.cmake:75 (message):
      Host compiler appears to require libatomic, but cannot find it.

Interestingly, Phase1 does *not* suffer from this, but there the "host
compiler" is clang 6.0.0.

Phase1 CMake output:

    Performing C++ SOURCE FILE Test HAVE_CXX_ATOMICS64_WITHOUT_LIB succeeded
with the following output:
    Change Dir:
/home/dim/llvm/7.0.0/rc1/Phase1/Release/llvmCore-7.0.0-rc1.obj/CMakeFiles/CMakeTmp

    Run Build Command:"/usr/local/bin/gmake"
"cmTC_845df/fast"
    /usr/local/bin/gmake -f CMakeFiles/cmTC_845df.dir/build.make
CMakeFiles/cmTC_845df.dir/build
    gmake[1]: Entering directory
'/home/dim/llvm/7.0.0/rc1/Phase1/Release/llvmCore-7.0.0-rc1.obj/CMakeFiles/CMakeTmp'
    Building CXX object CMakeFiles/cmTC_845df.dir/src.cxx.o
    /usr/bin/c++    -DHAVE_CXX_ATOMICS64_WITHOUT_LIB -std=c++11 
-Werror=unguarded-availability-new   -o CMakeFiles/cmTC_845df.dir/src.cxx.o -c
/home/dim/llvm/7.0.0/rc1/Phase1/Release/llvmCore-7.0.0-rc1.obj/CMakeFiles/CMakeTmp/src.cxx
    Linking CXX executable cmTC_845df
    /usr/local/bin/cmake -E cmake_link_script CMakeFiles/cmTC_845df.dir/link.txt
--verbose=1
    /usr/bin/c++   -DHAVE_CXX_ATOMICS64_WITHOUT_LIB -std=c++11 
-Werror=unguarded-availability-new    CMakeFiles/cmTC_845df.dir/src.cxx.o  -o
cmTC_845df -lm
    gmake[1]: Leaving directory
'/home/dim/llvm/7.0.0/rc1/Phase1/Release/llvmCore-7.0.0-rc1.obj/CMakeFiles/CMakeTmp'

    Source file was:

    #include <atomic>
    #include <cstdint>
    std::atomic<uint64_t> x (0);
    int main() {
      uint64_t i = x.load(std::memory_order_relaxed);
      return 0;
    }

Phase2 CMake output:

    Performing C++ SOURCE FILE Test HAVE_CXX_ATOMICS64_WITHOUT_LIB failed with
the following output:
    Change Dir:
/home/dim/llvm/7.0.0/rc1/Phase2/Release/llvmCore-7.0.0-rc1.obj/CMakeFiles/CMakeTmp

    Run Build Command:"/usr/local/bin/gmake"
"cmTC_720f3/fast"
    /usr/local/bin/gmake -f CMakeFiles/cmTC_720f3.dir/build.make
CMakeFiles/cmTC_720f3.dir/build
    gmake[1]: Entering directory
'/home/dim/llvm/7.0.0/rc1/Phase2/Release/llvmCore-7.0.0-rc1.obj/CMakeFiles/CMakeTmp'
    Building CXX object CMakeFiles/cmTC_720f3.dir/src.cxx.o
   
/home/dim/llvm/7.0.0/rc1/Phase1/Release/llvmCore-7.0.0-rc1.install/usr/local/bin/clang++
-DHAVE_CXX_ATOMICS64_WITHOUT_LIB -std=c++11  -Werror=unguarded-availability-new 
-o CMakeFiles/cmTC_720f3.dir/src.cxx.o -c
/home/dim/llvm/7.0.0/rc1/Phase2/Release/llvmCore-7.0.0-rc1.obj/CMakeFiles/CMakeTmp/src.cxx
    Linking CXX executable cmTC_720f3
    /usr/local/bin/cmake -E cmake_link_script CMakeFiles/cmTC_720f3.dir/link.txt
--verbose=1
   
/home/dim/llvm/7.0.0/rc1/Phase1/Release/llvmCore-7.0.0-rc1.install/usr/local/bin/clang++
-DHAVE_CXX_ATOMICS64_WITHOUT_LIB -std=c++11  -Werror=unguarded-availability-new 
CMakeFiles/cmTC_720f3.dir/src.cxx.o  -o cmTC_720f3 -lm
    CMakeFiles/cmTC_720f3.dir/src.cxx.o: In function `main':
    src.cxx:(.text+0x33): undefined reference to `__atomic_load_8'
    clang-7: error: linker command failed with exit code 1 (use -v to see
invocation)
    gmake[1]: *** [CMakeFiles/cmTC_720f3.dir/build.make:98: cmTC_720f3] Error 1
    gmake[1]: Leaving directory
'/home/dim/llvm/7.0.0/rc1/Phase2/Release/llvmCore-7.0.0-rc1.obj/CMakeFiles/CMakeTmp'
    gmake: *** [Makefile:126: cmTC_720f3/fast] Error 2

    Source file was:

    #include <atomic>
    #include <cstdint>
    std::atomic<uint64_t> x (0);
    int main() {
      uint64_t i = x.load(std::memory_order_relaxed);
      return 0;
    }

Apparently, with clang 6.0 it didn't generate libcalls to atomic functions,
but just put in cmpxchg8b's, I guess?  And with clang 7.0 this seems to have
changed.

For now, I can only test on amd64 due to this, since I don't have an easy
workaround.

-Dimitry

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 223 bytes
Desc: Message signed with OpenPGP
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20180805/8563f15e/attachment.sig>

Petr Hosek via llvm-dev

2018-Aug-06 00:41 UTC

head link

[llvm-dev] [Release-testers] [7.0.0 Release] rc1 has been tagged

On Sun, Aug 5, 2018 at 8:49 AM Dimitry Andric via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> On 3 Aug 2018, at 13:37, Hans Wennborg via Release-testers <
> release-testers at lists.llvm.org> wrote:
> >
> > 7.0.0-rc1 was just tagged (from the branch at r338847).
> >
> > It's early in the release process, but I'd like to find out
what the
> > status is of the branch on our various platforms.
> >
> > Please run the test script, share the results, and upload binaries.
>
> Hmm, I'm running into a rather nasty snag now on i386-freebsd11, due to
> our lack of atomic 64 bit primitives; Phase2's configure dies with:
>
>     -- Performing Test HAVE_CXX_ATOMICS_WITHOUT_LIB
>     -- Performing Test HAVE_CXX_ATOMICS_WITHOUT_LIB - Success
>     -- Performing Test HAVE_CXX_ATOMICS64_WITHOUT_LIB
>     -- Performing Test HAVE_CXX_ATOMICS64_WITHOUT_LIB - Failed
>     -- Looking for __atomic_load_8 in atomic
>     -- Looking for __atomic_load_8 in atomic - not found
>     CMake Error at cmake/modules/CheckAtomic.cmake:75 (message):
>       Host compiler appears to require libatomic, but cannot find it.
>
> Interestingly, Phase1 does *not* suffer from this, but there the "host
> compiler" is clang 6.0.0.
>
> Phase1 CMake output:
>
>     Performing C++ SOURCE FILE Test HAVE_CXX_ATOMICS64_WITHOUT_LIB
> succeeded with the following output:
>     Change Dir:
>
/home/dim/llvm/7.0.0/rc1/Phase1/Release/llvmCore-7.0.0-rc1.obj/CMakeFiles/CMakeTmp
>
>     Run Build Command:"/usr/local/bin/gmake"
"cmTC_845df/fast"
>     /usr/local/bin/gmake -f CMakeFiles/cmTC_845df.dir/build.make
> CMakeFiles/cmTC_845df.dir/build
>     gmake[1]: Entering directory
>
'/home/dim/llvm/7.0.0/rc1/Phase1/Release/llvmCore-7.0.0-rc1.obj/CMakeFiles/CMakeTmp'
>     Building CXX object CMakeFiles/cmTC_845df.dir/src.cxx.o
>     /usr/bin/c++    -DHAVE_CXX_ATOMICS64_WITHOUT_LIB -std=c++11
> -Werror=unguarded-availability-new   -o CMakeFiles/cmTC_845df.dir/src.cxx.o
> -c
>
/home/dim/llvm/7.0.0/rc1/Phase1/Release/llvmCore-7.0.0-rc1.obj/CMakeFiles/CMakeTmp/src.cxx
>     Linking CXX executable cmTC_845df
>     /usr/local/bin/cmake -E cmake_link_script
> CMakeFiles/cmTC_845df.dir/link.txt --verbose=1
>     /usr/bin/c++   -DHAVE_CXX_ATOMICS64_WITHOUT_LIB -std=c++11
> -Werror=unguarded-availability-new    CMakeFiles/cmTC_845df.dir/src.cxx.o
> -o cmTC_845df -lm
>     gmake[1]: Leaving directory
>
'/home/dim/llvm/7.0.0/rc1/Phase1/Release/llvmCore-7.0.0-rc1.obj/CMakeFiles/CMakeTmp'
>
>     Source file was:
>
>     #include <atomic>
>     #include <cstdint>
>     std::atomic<uint64_t> x (0);
>     int main() {
>       uint64_t i = x.load(std::memory_order_relaxed);
>       return 0;
>     }
>
> Phase2 CMake output:
>
>     Performing C++ SOURCE FILE Test HAVE_CXX_ATOMICS64_WITHOUT_LIB failed
> with the following output:
>     Change Dir:
>
/home/dim/llvm/7.0.0/rc1/Phase2/Release/llvmCore-7.0.0-rc1.obj/CMakeFiles/CMakeTmp
>
>     Run Build Command:"/usr/local/bin/gmake"
"cmTC_720f3/fast"
>     /usr/local/bin/gmake -f CMakeFiles/cmTC_720f3.dir/build.make
> CMakeFiles/cmTC_720f3.dir/build
>     gmake[1]: Entering directory
>
'/home/dim/llvm/7.0.0/rc1/Phase2/Release/llvmCore-7.0.0-rc1.obj/CMakeFiles/CMakeTmp'
>     Building CXX object CMakeFiles/cmTC_720f3.dir/src.cxx.o
>
>
/home/dim/llvm/7.0.0/rc1/Phase1/Release/llvmCore-7.0.0-rc1.install/usr/local/bin/clang++
>   -DHAVE_CXX_ATOMICS64_WITHOUT_LIB -std=c++11
> -Werror=unguarded-availability-new   -o CMakeFiles/cmTC_720f3.dir/src.cxx.o
> -c
>
/home/dim/llvm/7.0.0/rc1/Phase2/Release/llvmCore-7.0.0-rc1.obj/CMakeFiles/CMakeTmp/src.cxx
>     Linking CXX executable cmTC_720f3
>     /usr/local/bin/cmake -E cmake_link_script
> CMakeFiles/cmTC_720f3.dir/link.txt --verbose=1
>
>
/home/dim/llvm/7.0.0/rc1/Phase1/Release/llvmCore-7.0.0-rc1.install/usr/local/bin/clang++
>  -DHAVE_CXX_ATOMICS64_WITHOUT_LIB -std=c++11
> -Werror=unguarded-availability-new    CMakeFiles/cmTC_720f3.dir/src.cxx.o
> -o cmTC_720f3 -lm
>     CMakeFiles/cmTC_720f3.dir/src.cxx.o: In function `main':
>     src.cxx:(.text+0x33): undefined reference to `__atomic_load_8'
>     clang-7: error: linker command failed with exit code 1 (use -v to see
> invocation)
>     gmake[1]: *** [CMakeFiles/cmTC_720f3.dir/build.make:98: cmTC_720f3]
> Error 1
>     gmake[1]: Leaving directory
>
'/home/dim/llvm/7.0.0/rc1/Phase2/Release/llvmCore-7.0.0-rc1.obj/CMakeFiles/CMakeTmp'
>     gmake: *** [Makefile:126: cmTC_720f3/fast] Error 2
>
>     Source file was:
>
>     #include <atomic>
>     #include <cstdint>
>     std::atomic<uint64_t> x (0);
>     int main() {
>       uint64_t i = x.load(std::memory_order_relaxed);
>       return 0;
>     }
>
> Apparently, with clang 6.0 it didn't generate libcalls to atomic
> functions, but just put in cmpxchg8b's, I guess?  And with clang 7.0
this
> seems to have changed.
>
> For now, I can only test on amd64 due to this, since I don't have an
easy
> workaround.
>
Couldn't it be the consequence of
https://github.com/llvm-mirror/compiler-rt/commit/e8b47a537f4c849e66e450dadddfbfe03d1f06fd#diff-376935638380b425bdd8d9c735545491
?
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20180805/1e1b1156/attachment.html>

Hans Wennborg via llvm-dev

2018-Aug-06 16:23 UTC

head link

[llvm-dev] [Release-testers] [7.0.0 Release] rc1 has been tagged

On Sun, Aug 5, 2018 at 5:49 PM, Dimitry Andric <dimitry at andric.com>
wrote:> On 3 Aug 2018, at 13:37, Hans Wennborg via Release-testers
<release-testers at lists.llvm.org> wrote:
>>
>> 7.0.0-rc1 was just tagged (from the branch at r338847).
>>
>> It's early in the release process, but I'd like to find out
what the
>> status is of the branch on our various platforms.
>>
>> Please run the test script, share the results, and upload binaries.
>
> Hmm, I'm running into a rather nasty snag now on i386-freebsd11, due to
our lack of atomic 64 bit primitives; Phase2's configure dies with:
>
>     -- Performing Test HAVE_CXX_ATOMICS_WITHOUT_LIB
>     -- Performing Test HAVE_CXX_ATOMICS_WITHOUT_LIB - Success
>     -- Performing Test HAVE_CXX_ATOMICS64_WITHOUT_LIB
>     -- Performing Test HAVE_CXX_ATOMICS64_WITHOUT_LIB - Failed
>     -- Looking for __atomic_load_8 in atomic
>     -- Looking for __atomic_load_8 in atomic - not found
>     CMake Error at cmake/modules/CheckAtomic.cmake:75 (message):
>       Host compiler appears to require libatomic, but cannot find it.
>
> Interestingly, Phase1 does *not* suffer from this, but there the "host
compiler" is clang 6.0.0.
>
> Phase1 CMake output:
>
>     Performing C++ SOURCE FILE Test HAVE_CXX_ATOMICS64_WITHOUT_LIB
succeeded with the following output:
>     Change Dir:
/home/dim/llvm/7.0.0/rc1/Phase1/Release/llvmCore-7.0.0-rc1.obj/CMakeFiles/CMakeTmp
>
>     Run Build Command:"/usr/local/bin/gmake"
"cmTC_845df/fast"
>     /usr/local/bin/gmake -f CMakeFiles/cmTC_845df.dir/build.make
CMakeFiles/cmTC_845df.dir/build
>     gmake[1]: Entering directory
'/home/dim/llvm/7.0.0/rc1/Phase1/Release/llvmCore-7.0.0-rc1.obj/CMakeFiles/CMakeTmp'
>     Building CXX object CMakeFiles/cmTC_845df.dir/src.cxx.o
>     /usr/bin/c++    -DHAVE_CXX_ATOMICS64_WITHOUT_LIB -std=c++11 
-Werror=unguarded-availability-new   -o CMakeFiles/cmTC_845df.dir/src.cxx.o -c
/home/dim/llvm/7.0.0/rc1/Phase1/Release/llvmCore-7.0.0-rc1.obj/CMakeFiles/CMakeTmp/src.cxx
>     Linking CXX executable cmTC_845df
>     /usr/local/bin/cmake -E cmake_link_script
CMakeFiles/cmTC_845df.dir/link.txt --verbose=1
>     /usr/bin/c++   -DHAVE_CXX_ATOMICS64_WITHOUT_LIB -std=c++11 
-Werror=unguarded-availability-new    CMakeFiles/cmTC_845df.dir/src.cxx.o  -o
cmTC_845df -lm
>     gmake[1]: Leaving directory
'/home/dim/llvm/7.0.0/rc1/Phase1/Release/llvmCore-7.0.0-rc1.obj/CMakeFiles/CMakeTmp'
>
>     Source file was:
>
>     #include <atomic>
>     #include <cstdint>
>     std::atomic<uint64_t> x (0);
>     int main() {
>       uint64_t i = x.load(std::memory_order_relaxed);
>       return 0;
>     }
>
> Phase2 CMake output:
>
>     Performing C++ SOURCE FILE Test HAVE_CXX_ATOMICS64_WITHOUT_LIB failed
with the following output:
>     Change Dir:
/home/dim/llvm/7.0.0/rc1/Phase2/Release/llvmCore-7.0.0-rc1.obj/CMakeFiles/CMakeTmp
>
>     Run Build Command:"/usr/local/bin/gmake"
"cmTC_720f3/fast"
>     /usr/local/bin/gmake -f CMakeFiles/cmTC_720f3.dir/build.make
CMakeFiles/cmTC_720f3.dir/build
>     gmake[1]: Entering directory
'/home/dim/llvm/7.0.0/rc1/Phase2/Release/llvmCore-7.0.0-rc1.obj/CMakeFiles/CMakeTmp'
>     Building CXX object CMakeFiles/cmTC_720f3.dir/src.cxx.o
>    
/home/dim/llvm/7.0.0/rc1/Phase1/Release/llvmCore-7.0.0-rc1.install/usr/local/bin/clang++
-DHAVE_CXX_ATOMICS64_WITHOUT_LIB -std=c++11  -Werror=unguarded-availability-new 
-o CMakeFiles/cmTC_720f3.dir/src.cxx.o -c
/home/dim/llvm/7.0.0/rc1/Phase2/Release/llvmCore-7.0.0-rc1.obj/CMakeFiles/CMakeTmp/src.cxx
>     Linking CXX executable cmTC_720f3
>     /usr/local/bin/cmake -E cmake_link_script
CMakeFiles/cmTC_720f3.dir/link.txt --verbose=1
>    
/home/dim/llvm/7.0.0/rc1/Phase1/Release/llvmCore-7.0.0-rc1.install/usr/local/bin/clang++
-DHAVE_CXX_ATOMICS64_WITHOUT_LIB -std=c++11  -Werror=unguarded-availability-new 
CMakeFiles/cmTC_720f3.dir/src.cxx.o  -o cmTC_720f3 -lm
>     CMakeFiles/cmTC_720f3.dir/src.cxx.o: In function `main':
>     src.cxx:(.text+0x33): undefined reference to `__atomic_load_8'
>     clang-7: error: linker command failed with exit code 1 (use -v to see
invocation)
>     gmake[1]: *** [CMakeFiles/cmTC_720f3.dir/build.make:98: cmTC_720f3]
Error 1
>     gmake[1]: Leaving directory
'/home/dim/llvm/7.0.0/rc1/Phase2/Release/llvmCore-7.0.0-rc1.obj/CMakeFiles/CMakeTmp'
>     gmake: *** [Makefile:126: cmTC_720f3/fast] Error 2
>
>     Source file was:
>
>     #include <atomic>
>     #include <cstdint>
>     std::atomic<uint64_t> x (0);
>     int main() {
>       uint64_t i = x.load(std::memory_order_relaxed);
>       return 0;
>     }
>
> Apparently, with clang 6.0 it didn't generate libcalls to atomic
functions, but just put in cmpxchg8b's, I guess?  And with clang 7.0 this
seems to have changed.
>
> For now, I can only test on amd64 due to this, since I don't have an
easy workaround.
This doesn't sound so good, but I'm glad we found out early.

Did you file a bug to track this? (Sorry if you already did, I haven't
read through the list today.)

Thanks,
Hans

Dimitry Andric via llvm-dev

2018-Aug-07 20:17 UTC

head link

[llvm-dev] [Release-testers] [7.0.0 Release] rc1 has been tagged

On 3 Aug 2018, at 13:37, Hans Wennborg via Release-testers <release-testers
at lists.llvm.org> wrote:> 
> Dear testers,
> 
> 7.0.0-rc1 was just tagged (from the branch at r338847).
> 
> It's early in the release process, but I'd like to find out what
the
> status is of the branch on our various platforms.
> 
> Please run the test script, share the results, and upload binaries.
I've built and tested for FreeBSD 11 (a.k.a 11-STABLE) this time, since
FreeBSD 10 will be going EOL pretty soon now.  Uploaded:

SHA256 (clang+llvm-7.0.0-rc1-amd64-unknown-freebsd11.tar.xz) =
ed3191635be26cced8c75d5e57ff7e559f44b927a64c10d22611d8d912cf6df4

I posted the full test results here:

https://gist.github.com/DimitryAndric/64e9a7805a01e6027e2aaabfcda42bed

Summary:
  Expected Passes    : 50388
  Expected Failures  : 233
  Unsupported Tests  : 3687
  Unexpected Passes  : 1
  Unexpected Failures: 2490

The failures are distributed as follows:

  2028 libc++
   205 AddressSanitizer-i386-freebsd-dynamic
   200 AddressSanitizer-x86_64-freebsd-dynamic
    20 XRay-Unit
    11 MemorySanitizer-Unit
     7 lldb-Suite
     4 libunwind
     3 XRay-x86_64-freebsd
     3 lldb
     2 ThreadSanitizer-x86_64
     2 UBSan-MemorySanitizer-x86_64
     2 libFuzzer
     1 SanitizerCommon-asan-i386-FreeBSD
     1 SanitizerCommon-asan-x86_64-FreeBSD
     1 libomp

Almost all libc++ failures are due to FreeBSD missing timespec_get(),
and this became mandatory with https://reviews.llvm.org/rL338419:

In file included from
/home/dim/llvm/7.0.0/rc1/llvm.src/projects/libcxx/test/libcxx/containers/unord/next_pow2.pass.cpp:26:
In file included from
/home/dim/llvm/7.0.0/rc1/llvm.src/projects/libcxx/include/iostream:38:
In file included from
/home/dim/llvm/7.0.0/rc1/llvm.src/projects/libcxx/include/ios:216:
In file included from
/home/dim/llvm/7.0.0/rc1/llvm.src/projects/libcxx/include/__locale:18:
In file included from
/home/dim/llvm/7.0.0/rc1/llvm.src/projects/libcxx/include/mutex:191:
In file included from
/home/dim/llvm/7.0.0/rc1/llvm.src/projects/libcxx/include/__mutex_base:15:
In file included from
/home/dim/llvm/7.0.0/rc1/llvm.src/projects/libcxx/include/chrono:795:
/home/dim/llvm/7.0.0/rc1/llvm.src/projects/libcxx/include/ctime:77:9: error: no
member named 'timespec_get' in the global namespace; did you mean
'timespec'?
using ::timespec_get;
      ~~^~~~~~~~~~~~
        timespec
/usr/include/sys/_timespec.h:44:8: note: 'timespec' declared here
struct timespec {
       ^

We're tracking this in FreeBSD here: https://bugs.freebsd.org/230400,
but for existing FreeBSD releases this isn't fixable, so we could really
use some sort of workaround in libc++. :-)

-Dimitry

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 223 bytes
Desc: Message signed with OpenPGP
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20180807/685d0707/attachment.sig>

Louis Dionne via llvm-dev

2018-Aug-07 20:38 UTC

head link

[llvm-dev] [Release-testers] [7.0.0 Release] rc1 has been tagged

> On Aug 7, 2018, at 16:17, Dimitry Andric via llvm-dev <llvm-dev at
lists.llvm.org> wrote:
> 
> On 3 Aug 2018, at 13:37, Hans Wennborg via Release-testers
<release-testers at lists.llvm.org> wrote:
>> 
>> Dear testers,
>> 
>> 7.0.0-rc1 was just tagged (from the branch at r338847).
>> 
>> It's early in the release process, but I'd like to find out
what the
>> status is of the branch on our various platforms.
>> 
>> Please run the test script, share the results, and upload binaries.
> 
> I've built and tested for FreeBSD 11 (a.k.a 11-STABLE) this time, since
> FreeBSD 10 will be going EOL pretty soon now.  Uploaded:
> 
> SHA256 (clang+llvm-7.0.0-rc1-amd64-unknown-freebsd11.tar.xz) =
ed3191635be26cced8c75d5e57ff7e559f44b927a64c10d22611d8d912cf6df4
> 
> I posted the full test results here:
> 
> https://gist.github.com/DimitryAndric/64e9a7805a01e6027e2aaabfcda42bed
> 
> Summary:
>  Expected Passes    : 50388
>  Expected Failures  : 233
>  Unsupported Tests  : 3687
>  Unexpected Passes  : 1
>  Unexpected Failures: 2490
> 
> The failures are distributed as follows:
> 
>  2028 libc++
>   205 AddressSanitizer-i386-freebsd-dynamic
>   200 AddressSanitizer-x86_64-freebsd-dynamic
>    20 XRay-Unit
>    11 MemorySanitizer-Unit
>     7 lldb-Suite
>     4 libunwind
>     3 XRay-x86_64-freebsd
>     3 lldb
>     2 ThreadSanitizer-x86_64
>     2 UBSan-MemorySanitizer-x86_64
>     2 libFuzzer
>     1 SanitizerCommon-asan-i386-FreeBSD
>     1 SanitizerCommon-asan-x86_64-FreeBSD
>     1 libomp
> 
> Almost all libc++ failures are due to FreeBSD missing timespec_get(),
> and this became mandatory with https://reviews.llvm.org/rL338419:
> 
> In file included from
/home/dim/llvm/7.0.0/rc1/llvm.src/projects/libcxx/test/libcxx/containers/unord/next_pow2.pass.cpp:26:
> In file included from
/home/dim/llvm/7.0.0/rc1/llvm.src/projects/libcxx/include/iostream:38:
> In file included from
/home/dim/llvm/7.0.0/rc1/llvm.src/projects/libcxx/include/ios:216:
> In file included from
/home/dim/llvm/7.0.0/rc1/llvm.src/projects/libcxx/include/__locale:18:
> In file included from
/home/dim/llvm/7.0.0/rc1/llvm.src/projects/libcxx/include/mutex:191:
> In file included from
/home/dim/llvm/7.0.0/rc1/llvm.src/projects/libcxx/include/__mutex_base:15:
> In file included from
/home/dim/llvm/7.0.0/rc1/llvm.src/projects/libcxx/include/chrono:795:
> /home/dim/llvm/7.0.0/rc1/llvm.src/projects/libcxx/include/ctime:77:9:
error: no member named 'timespec_get' in the global namespace; did you
mean 'timespec'?
> using ::timespec_get;
>      ~~^~~~~~~~~~~~
>        timespec
> /usr/include/sys/_timespec.h:44:8: note: 'timespec' declared here
> struct timespec {
>       ^
> 
> We're tracking this in FreeBSD here: https://bugs.freebsd.org/230400,
> but for existing FreeBSD releases this isn't fixable, so we could
really
> use some sort of workaround in libc++. :-)
Ugh. The problem here is that libc++ checks whether the underlying C standard
library implementation has support for C11 as a whole, not on a
function-by-function basis. This means that the easiest workaround is to pretend
that FreeBSD does NOT support C11 as a whole, but that is going to be a
regression from prior releases, which provided a subset of C11 through libc++.

Generally, I think supporting things on a per-platform basis like this is a bad
idea because it becomes a complete maze. Perhaps the current situation justifies
a workaround, perhaps only targeted to the LLVM 7 branch. Marshall, what’s your
opinion?

Louis
> 
> -Dimitry
> 
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

Jonas Hahnfeld via llvm-dev

2018-Aug-07 21:01 UTC

head link

[llvm-dev] [7.0.0 Release] rc1 has been tagged

On 2018-08-03 13:37, Hans Wennborg via llvm-dev wrote:> Dear testers,
> 
> 7.0.0-rc1 was just tagged (from the branch at r338847).
> 
> It's early in the release process, but I'd like to find out what
the
> status is of the branch on our various platforms.
> 
> Please run the test script, share the results, and upload binaries.
I tested with test-release.sh on CentOS (x86_64) and results were pretty 
good:
  - Two failing tests in check-all because the system didn't have a 
static 32bit libstdc++.a (I usually don't build and test 32bit 
compiler-rt).
  - One build failure in test-suite because it was using the outdated 
<complex> header from gcc 4.8.5: It appears real() and imaginary() are 
not declared const in there.

Today I fired our internal install script and found a whole lot of 
errors in LLDB. Is there a reason LLDB is disabled in test-release.sh?
(For reference Michal already reported some of the failing tests in 
https://bugs.llvm.org/show_bug.cgi?id=38453, 
https://bugs.llvm.org/show_bug.cgi?id=38456, and 
https://bugs.llvm.org/show_bug.cgi?id=38457. I can dig up the full log 
if needed, I've for now disabled installation of the debugger.)

Cheers,
Jonas

Brian Cain via llvm-dev

2018-Aug-18 04:00 UTC

head link

[llvm-dev] [Release-testers] [7.0.0 Release] rc1 has been tagged

SLES11 rc1 build failed, opened PR38589.

Uploaded SLES12 rc1:
39ba1263db364999357fae8c6f2829b8fce7cfdd
clang+llvm-7.0.0-rc1-x86_64-linux-sles12.3.tar.xz



On Fri, Aug 3, 2018 at 6:38 AM Hans Wennborg via Release-testers <
release-testers at lists.llvm.org> wrote:
> Dear testers,
>
> 7.0.0-rc1 was just tagged (from the branch at r338847).
>
> It's early in the release process, but I'd like to find out what
the
> status is of the branch on our various platforms.
>
> Please run the test script, share the results, and upload binaries.
>
> Thanks,
> Hans
> _______________________________________________
> Release-testers mailing list
> Release-testers at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>

-- 
-Brian
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20180817/3bd11635/attachment.html>

llvm dev - Aug 2018 - [Release-testers] [7.0.0 Release] rc1 has been tagged

[llvm-dev] [7.0.0 Release] rc1 has been tagged

[llvm-dev] [cfe-dev] [7.0.0 Release] rc1 has been tagged

[llvm-dev] [cfe-dev] [7.0.0 Release] rc1 has been tagged

[llvm-dev] [7.0.0 Release] rc1 has been tagged

[llvm-dev] [Release-testers] [7.0.0 Release] rc1 has been tagged

[llvm-dev] [Release-testers] [7.0.0 Release] rc1 has been tagged

[llvm-dev] [Release-testers] [7.0.0 Release] rc1 has been tagged

[llvm-dev] [Release-testers] [7.0.0 Release] rc1 has been tagged

[llvm-dev] [Release-testers] [7.0.0 Release] rc1 has been tagged

[llvm-dev] [7.0.0 Release] rc1 has been tagged

[llvm-dev] [Release-testers] [7.0.0 Release] rc1 has been tagged