similar to: llvm.org pre-built clang significantly slower than apple/xcode clang

Displaying 20 results from an estimated 2000 matches similar to: "llvm.org pre-built clang significantly slower than apple/xcode clang"

2018 Nov 20
2
[cfe-dev] llvm.org pre-built clang significantly slower than apple/xcode clang
I don’t think Apple disable assertion on the release build. I remember having clang and llvm crash because of assertion failure regularly at some point in the past. Nowadays, it is far more unusual to get a clang crash, so I can’t tell, but I doubt they change the configuration. > Le 20 nov. 2018 à 16:32, Jack Howarth via cfe-dev <cfe-dev at lists.llvm.org> a écrit : > > The
2016 May 28
2
[LibFuzzer] Recent performance regression due to r270942
Hi, This started as an off hand comment in [1] but this appears to be a real issue so I'm moving the discussion to the mailing list. In r270942 the time taken to run LibFuzzer's test became noticeably longer. I am building on * Arch Linux (4.5.4-1-ARCH #1 SMP PREEMPT Wed May 11 22:21:28 CEST 2016 x86_64 GNU/Linux) * I am building libFuzzer and running its tests like so ```
2016 May 28
0
[LibFuzzer] Recent performance regression due to r270942
Reproduced, should be easy to fix. Will do it. And thanks for noticing, on my machine this fails very fast and the test passes because it sees everything it wants to see. --kcc On Fri, May 27, 2016 at 6:18 PM, Dan Liew <dan at su-root.co.uk> wrote: > Hi, > > This started as an off hand comment in [1] but this appears to be a > real issue so I'm moving the discussion to the
2020 Jul 23
2
How to debug a missing symbol with ThinLTO?
Hi Tobias The problem is that your static archive has a SYMDEF that is empty, so linker thinks the static library provided doesn't contain any symbol. The reason for that is you are using the `ranlib` from Xcode, which is too old to understand the new bitcode object files produced by llvm 10. There are lots of ways to fix that: * The standard way to create static library on macOS is to use
2020 Jul 22
2
How to debug a missing symbol with ThinLTO?
Looks like your static library is not even pulled into the link command so the static library is not even in the snapshot. From the link command in the snapshot, the static library is not on the command line from snapshot: /Applications/Xcode-11.3.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld -Z -demangle -object_path_lto
2015 Sep 18
3
LLVM and XCode 7.0.0
After upgrading today to xcode 7, a bunch of my cmake build files stopped working, because we went from $ clang --version Apple LLVM version 6.1.0 (clang-602.0.53) (based on LLVM 3.6.0svn) to $ clang --version Apple LLVM version 7.0.0 (clang-700.0.72) See, so now anything that parsed this output to make decisions based on the underlying llvm/clang version no longer works,
2020 Jul 22
2
How to debug a missing symbol with ThinLTO?
This is usually a problem that is not using llvm-ar. I cannot reproduce this problem with either llvm 10.0 or TOT version. Which linker version are you using? You can also try pass "-Wl,-debug_snapshot" to the command where the error produces and then locate the "*.ld-snapshot" in /tmp directory and attach that as a reproducer. Steven > On Jul 22, 2020, at 8:41 AM, Teresa
2020 Jul 22
2
How to debug a missing symbol with ThinLTO?
David, Thanks for looking into this. I did a small reproduction on my machine outside of my build system. So here is how to reproduce: Download https://downloads.xiph.org/releases/ogg/libogg-1.3.4.tar.xz Download llvm-10.0.1 macOS binary export PATH=<path to llvm/bin>:$PATH export SDKROOT=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk untar
2020 Sep 30
5
[Release-testers] [11.0.0 Release] Release Candidate 5 is here
I’m happy to run them, although I’d appreciate a pointer to the appropriate documentation. From: llvm-dev <llvm-dev-bounces at lists.llvm.org> on behalf of Tobias Hieta via llvm-dev <llvm-dev at lists.llvm.org> Reply-To: Tobias Hieta <tobias at plexapp.com> Date: Wednesday, September 30, 2020 at 11:15 AM To: Hans Wennborg <hans at chromium.org> Cc: llvm-dev <llvm-dev at
2019 Oct 17
4
llvm-strip creates unloadable shared objects on linux-armv7hf
Hello Rui, Thanks for your reply. I tried with the keep-section argument and that made the shared library work. Should these sections be kept around by default maybe? -- Tobias On Thu, Oct 17, 2019 at 11:06 AM Rui Ueyama <ruiu at google.com> wrote: > > One thing I noticed is that llvm-strip seemed to remove a .ARM.attributes section. Can you try --keep-section=.ARM.attributes to
2019 Oct 18
2
llvm-strip creates unloadable shared objects on linux-armv7hf
Jordan, I have sent the patch via Phabricator: https://reviews.llvm.org/D69188 Let me know if I got it right. -- Tobias On Thu, Oct 17, 2019 at 7:12 PM Jordan Rupprecht <rupprecht at google.com> wrote: > > Tobias, > I don't have much experience with ARM, but from your report and Peter's explanation of why LLD does it, I agree we should be consistent with LLD and keep the
2020 Feb 03
2
ASAN not finding any bugs?
Hello Alex, Thanks for the hint. It was actually not the -O flag that created the problem. But it pointed me in the right direction, when I passed -fno-experimental-new-pass-manager it started to show the error. My guess is that the new pass manager is more aggressive in removing UB? Thanks, Tobias On Mon, Feb 3, 2020 at 5:29 PM Alex Brachet-Mialot <alexbrachetmialot at gmail.com> wrote:
2019 Oct 17
2
llvm-strip creates unloadable shared objects on linux-armv7hf
Hello Tobias, I think that looks reasonable to me, I think it will be down to the llvm-objcopy team whether they want to make .ARM.attributes a special case or not. The best way to find out is to submit a patch, citing the problems with old versions of libc, I'd expect that you'll need to add a test case for the patch to be accepted. To do that it is probably best to look at the existing
2020 Sep 10
2
[RFC] New Feature Proposal: De-Optimizing Cold Functions using PGO Info
FYI David is referring to PGSO (profile-guided size optimization) as it exists directly under that name, see: https://reviews.llvm.org/D67120. And yeah using PGSO is selecting optsize while this change is selecting optnone. On 9/9/20, 10:58 AM, "llvm-dev on behalf of Tobias Hieta via llvm-dev" <llvm-dev-bounces at lists.llvm.org<mailto:llvm-dev-bounces at lists.llvm.org> on
2010 Nov 01
3
btrfs benchmark with 2.6.37-rc1
Here is a small btrfs vs. ext4 benchmark with kernel 2.6.37-rc1. compilebench with options -i 10 -r 30 on 2.6.37-rc1 btrfs ========================================================================== intial create total runs 10 avg 73.11 MB/s (user 0.34s sys 1.96s) create total runs 5 avg 49.53 MB/s (user 0.41s sys 1.62s) patch total runs 4 avg 22.13 MB/s (user 0.09s sys 1.79s) compile total runs
2020 Jul 22
2
How to debug a missing symbol with ThinLTO?
Hello, I am building libogg with clang (10.0.1) on macOS and if I pass "-flto=thin" to C and LDFLAGS it will not link correctly claiming missing symbols when linking to the archive (libogg.a). undef: _ogg_stream_init Undefined symbols for architecture x86_64: "_ogg_stream_init", referenced from: _main in lto.o Removing lto=thin fixes the problem. Inspecting the AR libs with
2019 Jan 24
2
LLVM/Clang 8.0.0-rc1 source tarballs?
Thanks for the information Tobias. - Sedat - On Thu, Jan 24, 2019 at 3:31 PM Tobias Hieta <tobias at plexapp.com> wrote: > > Sedat, > > In Hans announcement yesterday he pointed out that he would upload source tarballs as soon as possible: > > "I'll get the source tarballs and docs published as soon as possible, and binaries as they become available" >
2020 Mar 24
6
LLVM 10.0.0 Release
I am pleased to announce that LLVM 10 is now available. Get it here: https://llvm.org/releases/download.html#10.0.0 This release is the result of the LLVM community's work over the past six months (up to to e26a78e7085 on master plus commits up to d32170dbd5b on the release/10.x branch). Some highlights include: - C++ Concepts support in Clang - Clang no longer runs in a separate process
2020 Mar 24
6
LLVM 10.0.0 Release
I am pleased to announce that LLVM 10 is now available. Get it here: https://llvm.org/releases/download.html#10.0.0 This release is the result of the LLVM community's work over the past six months (up to to e26a78e7085 on master plus commits up to d32170dbd5b on the release/10.x branch). Some highlights include: - C++ Concepts support in Clang - Clang no longer runs in a separate process
2019 Dec 10
2
[Release-testers] LLVM 9.0.1-rc2 has been tagged
On 12/10/2019 12:06 AM, Tobias Hieta wrote: > Hello, > > I finally figured out that I still need Python 2.7 in order to get > tests running correctly on macOS. But this lead to a bunch of test > fails when using the script: > > FAIL: LLVM :: Bindings/Go/go.test (23671 of 61786) I've seen this go failure before on macOS, so it is somewhat expected. Do the rest of these