search for: shealevi

On 05/02/2012 01:00 PM, Dave Zarzycki wrote: > Shea, > > Feasible? Sure, anything is feasible. A good idea? Not really. The internal lld file format is an _intermediate_ data structure designed to make creating the final executable straightforward and fast. It isn't designed to be an executable format itself. In fact, the reason why linkers can often be slow is because the

Shea, Feasible? Sure, anything is feasible. A good idea? Not really. The internal lld file format is an _intermediate_ data structure designed to make creating the final executable straightforward and fast. It isn't designed to be an executable format itself. In fact, the reason why linkers can often be slow is because the intermediate and final object file formats are conflated. davez On

On 10/19/11 11:58 PM, Eli Friedman wrote: > On Wed, Oct 19, 2011 at 8:20 PM, Shea Levy<shea at shealevy.com> wrote: >> 2. Are target-specific behaviors documented for each supported target? > When anything has target-specific behavior, that fact should be > documented. Beyond that, if you have a question about what some > construct is supposed to do, please ask. What I

On Wed, Oct 19, 2011 at 8:20 PM, Shea Levy <shea at shealevy.com> wrote: > Hello, > > I'd like write a program that performs static analysis of code at the > LLVM assembly/bitcode level, and to do so I plan on extensively > referencing the language reference. As I hope to eventually use this > tool as part of a security analysis of untrusted code, I need to be >

On Thu, Oct 20, 2011 at 2:37 AM, Shea Levy <shea at shealevy.com> wrote: >. The > (probably impossible) end-goals to this project would be a) that every > program which passes its checks would be as safe to run in kernel mode > with full memory access as it would be in user mode That would be a very useful thing to have for embedded systems. Some such as uCLinux run ports of

Hello, I'd like write a program that performs static analysis of code at the LLVM assembly/bitcode level, and to do so I plan on extensively referencing the language reference. As I hope to eventually use this tool as part of a security analysis of untrusted code, I need to be rather strict in my interpretation of the document. As such, I have some questions about how the implementers

Hello, Would it be feasible to use the internal lld file format as the native executable format for an OS? Are there performance or space considerations that would make this a poor choice? Cheers, Shea Levy P.S. please CC me on replies, I'm not subscribed.

> > On Oct 20, 2011, at 3:13 AM, Shea Levy wrote: > >> Hello, >> >> The llvm 2.9 configure script fails to check for groff, causing a >> failure very late in the game when building man pages, and, on OSX, >> sw_vers. I'll try to write a patch for this myself, but autoconf is >> largely black magic to me so I thought I'd throw this out there in

On Oct 20, 2011, at 2:37 AM, Shea Levy wrote: > On 10/19/11 11:58 PM, Eli Friedman wrote: >> On Wed, Oct 19, 2011 at 8:20 PM, Shea Levy<shea at shealevy.com> wrote: >>> 2. Are target-specific behaviors documented for each supported target? >> When anything has target-specific behavior, that fact should be >> documented. Beyond that, if you have a question

https://bugs.freedesktop.org/show_bug.cgi?id=27501 Summary: nVidia 9600M GT (Macbook Pro current model) is unable to boot Product: xorg Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: critical Priority: medium Component: Driver/nouveau

flight 17325 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/17325/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl 9 guest-start fail REGR. vs. 12557 test-amd64-i386-xl-credit2 15 guest-stop fail REGR. vs. 12557 test-amd64-i386-xl 15 guest-stop

flight 17454 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/17454/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-pair 17 guest-migrate/src_host/dst_host fail REGR. vs. 12557 Regressions which are regarded as allowable (not blocking): test-amd64-i386-qemut-rhel6hvm-amd 7 redhat-install fail

flight 17612 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/17612/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-pair 17 guest-migrate/src_host/dst_host fail REGR. vs. 12557 Regressions which are regarded as allowable (not blocking): test-amd64-i386-rhel6hvm-intel 9 guest-start.2 fail

flight 17901 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/17901/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-qemuu-rhel6hvm-intel 4 xen-install fail REGR. vs. 12557 test-amd64-i386-pv 4 xen-install fail REGR. vs. 12557 test-amd64-amd64-pv 4

flight 17916 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/17916/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-pv 4 xen-install fail REGR. vs. 12557 test-amd64-amd64-xl 4 xen-install fail REGR. vs. 12557 test-amd64-amd64-xl-win7-amd64 4

flight 18150 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/18150/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-rhel6hvm-amd 7 redhat-install fail REGR. vs. 12557 test-amd64-i386-pair 17 guest-migrate/src_host/dst_host fail REGR. vs. 12557 Regressions which are regarded as

flight 18181 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/18181/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-rhel6hvm-amd 7 redhat-install fail REGR. vs. 12557 test-amd64-i386-pair 17 guest-migrate/src_host/dst_host fail REGR. vs. 12557 Regressions which are regarded as

flight 18805 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/18805/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-rhel6hvm-amd 7 redhat-install fail REGR. vs. 12557 test-amd64-i386-pair 17 guest-migrate/src_host/dst_host fail REGR. vs. 12557 Regressions which are regarded as

flight 18844 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/18844/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-i386 4 xen-build fail REGR. vs. 12557 Tests which did not succeed, but are not blocking: test-amd64-amd64-xl-pcipt-intel 9 guest-start fail

Hello, The llvm 2.9 configure script fails to check for groff, causing a failure very late in the game when building man pages, and, on OSX, sw_vers. I'll try to write a patch for this myself, but autoconf is largely black magic to me so I thought I'd throw this out there in case someone more experienced in this stuff wants to fix this. Cheers, Shea Levy