similar to: [LLVMdev] reporting LLVM bugs

Hi! Apparently there are no precompiled binaries for llvm-gcc 4.0 for Linux. I've tried downloading the sources and building according to http://llvm.org/docs/CFEBuildInstrs.html (except I'm not an elite gcc hacker). I tried following the guidelines and got what looks like a gcc for x86 with no traces of LLVM. I tried passing --enable-llvm with various llvm root pathnames and got ICEs.

Hi! Apparently llvm-gcc ignores #line directives in source files when generating debug information. When I compile this: //test int f(int a) { #line 1 "someplace" return a*a; } //end with `llvm -g -S lines.c`, `someplace' is not mentioned in lines.s. It also looks like functions #included from header files get attributed to the #including file (albeit at the right line number).

Hmm, today I just tried compiling the llvm-gcc 4.0 frontend again on linux (Fedora Core 3 I believe) and I seem to be suddenly having the problem that Yossi Kreinin mentioned. The frontend seems to be using normal gcc to compile as I no longer get a bytecode file after compilation. When I pass the --version argument it claims to be the LLVM 4.0.1 frontend. Any ideas what might cause this? It was

Hi! The LLVM Bytecode File Format specifies an optional SectionID attribute for globals. I didn't find a matching attribute in the LLVM source code. Code such as: int a __attribute__ ((section ("A_SECTION"))); compiles with llvm-gcc, but apparently the section information is stripped (the object file doesn't contain "A_SECTION"). Is the SectionID feature

Hi! I'm working on an LLVM back-end for a processor with a stack machine architecture. After experimenting with code generation directly from the LLVM representation, I'm studying the target-independant code generator. As far as I understand, there currently exists a target-independant infrastructure for legalization, instruction selection, scheduling and register allocation. It is clear

Hi John, llvm-gcc4 by default emits object files, just as gcc does. This is by design. If you want to get bytecode output you need to use the --emit- llvm-bc option. A complete list of the options that llvm-gcc4 supports can be obtained with "llvm-gcc -v --help" (lots of output). Here are the descriptions of the --emit-llvm options: -emit-llvm Emit LLVM code to the

On 6/3/06, Reid Spencer <reid at x10sys.com> wrote: > I don't think anyone has successfully built llvm-gcc4 on Linux yet. I've > tried and failed. I have :-) There was some patches, but I believe that they were all merged in the latest snapshot. Rafael

Chris asked me to write up "LLVM Developer's Guide to Dwarf Support" for LLVM maintainers. We are still in early stages, but we thought we'd get it out there for the "need to bleeders." At some point this information will be formalized and added to the LLVM documentation. The enclosed document gives specific instructions for adding source line number support

Hello people, me again ... Just an FYI this time, I think: 0[209]1 sunray1:/contrib > gtar zxf R-1.4.1.tgz tar: R-1.4.1/date-stamp: Could not create file: Permission denied gtar: Error exit delayed from previous errors 2[210]1 sunray1:/contrib > gtar zxvf R-1.4.1.tgz "R-1.4.1/date-stamp" R-1.4.1/date-stamp gtar: R-1.4.1/date-stamp: Could not create file: Permission denied gtar:

Hi I encountered this problem a few times in the past, but only now it is consistent enough so I can write this email. In short, the problem is that after I copy some structure from the profiled program to the dtrace space, and set a "this-dataP" variable to point to the local copy, after a while some of the fields of the local structure are overridden with junk values. In

Hello everyone two small questions with hopefully short answer. 1)How can I send simultaneously a massage to all members on the network using smbclient??? 2)smbtar does not back-up files and folders with hebrew names for those files/folders so....? Thanks: Yossi Shani -> shaniy@actcom.co.il

Hi I'm looking for code that implements the 802.1d spanning tree. Do you have an idea where can I download this code? Thanks Yossi -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.linux-foundation.org/pipermail/bridge/attachments/20050818/692b471a/attachment-0002.htm

I don't think anyone has successfully built llvm-gcc4 on Linux yet. I've tried and failed. The instructions in CFEBuildInstrs.html are for llvm-gcc3 and probably won't work as-is. Reid. On Sat, 2006-06-03 at 19:39 +0300, Yossi Kreinin wrote: > Hi! > > Apparently there are no precompiled binaries for llvm-gcc 4.0 for Linux. > > I've tried downloading the sources

I have some folders with a good amount of spam. While demonstrating full text search to a user, we found a folder that would crash dovecot while doing a fts. While splitting up the mailbox to narrow it down, I found there are a good number of messages in that folder that all made it crash in the same manner. I figured I'd narrow down a single one, get that fixed, then retest the rest. I

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-07:10.gtar Security Advisory The FreeBSD Project Topic: gtar directory traversal vulnerability Category: contrib Module: contrib_tar Announced:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-07:10.gtar Security Advisory The FreeBSD Project Topic: gtar directory traversal vulnerability Category: contrib Module: contrib_tar Announced:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-06:26.gtar Security Advisory The FreeBSD Project Topic: gtar name mangling symlink vulnerability Category: contrib Module: contrib_tar

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-06:26.gtar Security Advisory The FreeBSD Project Topic: gtar name mangling symlink vulnerability Category: contrib Module: contrib_tar

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, if deliver is started with: deliver -f sender -d user (no -a option) and no Envelope-To header exists in the mail, two problems show up in this block in main(): if (destaddr == NULL) { destaddr = deliver_get_address(mail, "Envelope-To"); if (destaddr == NULL) { destaddr = strchr(user, '@') == NULL ? user :

My manifest includes this snippet class app_client_openbsd { $app_client_pkgs_obsd = [ ''glib2-2.24.1p2'', ''gtar-1.23p1'' ] package { "${app_client_pkgs_obsd}": ensure => ''installed'', source => "http://${installserver}/openbsd/${operatingsystemrelease}/packages/${hardwaremodel}/${name}.tgz", } This