similar to: archiving LTO objects broken for current Xcode releases

Displaying 20 results from an estimated 100 matches similar to: "archiving LTO objects broken for current Xcode releases"

2016 Oct 26
0
archiving LTO objects broken for current Xcode releases
> On Oct 26, 2016, at 8:06 AM, Jack Howarth via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > The ability to archive object files generated with -flto under > LLVM.org clang 3.9.0 or 4.0svn trunk is broken against the currently > shipping Xcode releases including the upcoming Xcode 8.1 GM. > > https://llvm.org/bugs/show_bug.cgi?id=30791 > > $ clang-3.9
2011 Jun 18
2
[LLVMdev] Cross compilation question
Hello, I wonder if it's possible to cross compile regular linux packages (autotools based) into llvm bitcode. Such bitcode could run on multiple target platforms using lli. So for example if we take 'tar' sources and compile them, we have 'tar' bitcode. We can run it using 'lli tar'. If it was possible in general, then probably building lots of linux packages could be
2011 Jun 20
0
[LLVMdev] Cross compilation question
Hi Rafal, LLVM's bitcode is not target independent in the manner you're hoping for. You can't take bitcode generated for x86 and use it on ARM, for example, or bitcode generated for Linux and use it on Darwin. -Jim On Jun 18, 2011, at 4:10 PM, Rafal Rusin wrote: > Hello, > > I wonder if it's possible to cross compile regular linux packages > (autotools based) into
2015 Dec 11
2
bitcode versioning
Hi Mehdi and my apologies for the delay in responding - the day job got in the way :-) Our target is still out-of-tree so my reasons for extending the IR would be eliminated if we were a proper part of LLVM, which I would like to do when the time is right for us. My extensions are quite simple really, and I expect that they will be wanted in the TRUNK sometime anyway. At the moment I only have
2013 Oct 11
0
CESA-2013:1418 Moderate CentOS 6 libtar Update
CentOS Errata and Security Advisory 2013:1418 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2013-1418.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 41fc0455025f594396fda1eda1f35a8762b281355b88accb670f65e8e7487188 libtar-1.2.11-17.el6_4.1.i686.rpm
2012 Apr 09
0
CEBA-2012:0462 CentOS 6 libtar FASTTRACK Update
CentOS Errata and Bugfix Advisory 2012:0462 Upstream details at : https://rhn.redhat.com/errata/RHBA-2012-0462.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: d15f7ea84184b8f8d786c5660cae58d2711852061765f51403a75fa0dda2f683 libtar-1.2.11-17.el6.i686.rpm
2017 Jan 06
2
LLD and LLVM_LINK_LLVM_DYLIB
It builds fine but I cannot execute the resulting binary which aborts with the mentioned error.However I don't use LLVM_ENABLE_PROJECTS, I don't know if that changes the way libLLVM-4.0svn.so is linked... Cheers,Jonas Am Freitag, den 06.01.2017, 13:44 +0900 schrieb Rui Ueyama: > Hi Hahnfeld, > I just compiled with LLVM_LINK_LLVM_DYLIB enabled [1] and build lld with `ninja lld`. It
2017 Jan 04
2
LLD and LLVM_LINK_LLVM_DYLIB
Hi all, I recently gave LLD a try and it definitely works fine. However one cannot build it together with LLVM_LINK_LLVM_DYLIB: ELF/Driver.cpp and ELF/DriverUtils.cpp pull in llvm/Support/CommandLine.h which defines the command line options so these global variables end up in libLLVM-4.0svn.so via liblldELF. If this shared library is then linked into bin/lld or bin/opt one gets errors because of
2015 May 18
0
CEBA-2015:1014 CentOS 7 libtar FASTTRACK BugFix Update
CentOS Errata and Bugfix Advisory 2015:1014 Upstream details at : https://rhn.redhat.com/errata/RHBA-2015-1014.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 79daf938d2f7c47f0d064ac8fb6b2735e72e307339da36165711ba3caf0cedbf libtar-1.2.11-29.el7.i686.rpm
2017 Jan 06
2
LLD and LLVM_LINK_LLVM_DYLIB
I've dealt with similar issues on the LLDB side, I think I can help you with this. pl On 6 January 2017 at 09:39, Rui Ueyama via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Thanks for the info. I can reproduce the issue. But because of lack of cmake > knowledge, I don't know how to fix that now. If no one will take a look at > this, I'll investigate it. > > On
2012 Apr 09
0
CentOS-announce Digest, Vol 86, Issue 5
Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When
2015 May 19
0
CentOS-announce Digest, Vol 123, Issue 6
Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When
2013 Oct 12
0
CentOS-announce Digest, Vol 104, Issue 5
Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When
2006 Apr 19
0
TRUGhat 2006:1
The Toronto Ruby User''s Group (TRUG) is pleased to announce TRUGhat 2006:1. TRUGhat: [T]oronto [R]uby [U]ser''s [G]roup [ha]cka[t]hon TRUGhat is TRUG''s hackathon[1] or codefest. In a hackathon, a group of people get together and will either work toward a common goal, or simply work in a common area on code that interests them. For our first TRUGhat, we have agreed
2015 Dec 02
2
fuzzer crash (but not the good kind)
Kostya, I think I've found what looks like a reproducible bug in libFuzzer. The code under test is built with ASan and the first ASan CHECK failure shows fuzzer in the stack trace. (see below) One of the factors that may be unique in my testing is that each iteration can take a very long time to execute (tens or hundreds of seconds). Let me know if you need more info, I think it
2007 Apr 30
5
Asterisk 1.4.4 VoiceMail ODBC Storage Help
Hi All, I have an issue with the ODBC voicemail storage option with asterisk. All appears to work fine, however, I get several sql execute warnings. I was wondering if anyone out there could help me get to the bottom of what is causing this and how I could possibly go about rectifying it. The warning message we are getting is as follows: WARNING[30115]: app_voicemail.c:1280 delete_file: SQL
2015 Dec 03
2
fuzzer crash (but not the good kind)
Kostya, Here's the git repo: https://bitbucket.org/ebadf/fuzzpy I've only tested it on arm7 and x86_64 linux, I expect there's a good chance it may not work on other OSs. If you can build it successfully ("./build.sh", requires clang and clang++ in your path), then you should run the "testemail" case like so: while true; do ITERS=1000 ./run.sh
2015 Dec 03
2
fuzzer crash (but not the good kind)
Ah, yes -- you need to clone with --recursive. I will try the workaround though. On Dec 3, 2015 1:12 PM, "Kostya Serebryany" <kcc at google.com> wrote: > > > On Wed, Dec 2, 2015 at 7:17 PM, Brian Cain <brian.cain at gmail.com> wrote: > >> Kostya, >> >> Here's the git repo: https://bitbucket.org/ebadf/fuzzpy >> >> I've only
2004 Oct 17
0
modify rsync: read files from a tar archive
Yodel! I'm trying to modify rsync so that it can read the source files from a tar archive instead of a file system. I want to use this so I can fetch whole filesystems from a fileserver with (i) a more efficient storage of the filesystem images on the server and above all (ii) the process fetching the filesystem image doesn't need any privileges on the fileserver (even if some of
2015 Jul 07
3
List S3 methods and defining packages
Hi, from the man page ?methods, I expected to be able to build pairs (class,package) for a given S3 method, e.g., print, using attr(methods(print), 'info'). However all the methods, except the ones defined in base or S4 methods, get the 'from' value "registered S3method for print", instead of the actual package name (see below for the first rows). Is this normal