Displaying 20 results from an estimated 10000 matches similar to: "[LLVMdev] Fwd: Removing GCC Runtime Dependencies on Linux"
2011 Dec 20
2
[LLVMdev] Fwd: Removing GCC Runtime Dependencies on Linux
On 12/19/11 7:19 PM, Howard Hinnant wrote:
> On Dec 19, 2011, at 7:14 PM, Shea Levy wrote:
>
>> Hello all,
>>
>> Is it possible, if using libc++ and compiler-rt, to have a clang with no
>> runtime dependencies on any GCC components on Linux? If not, will this
>> ever be possible?
> We are working on a new libc++abi: http://libcxxabi.llvm.org/ which carries
2011 Dec 20
0
[LLVMdev] Fwd: Removing GCC Runtime Dependencies on Linux
On Dec 19, 2011, at 7:14 PM, Shea Levy wrote:
> Hello all,
>
> Is it possible, if using libc++ and compiler-rt, to have a clang with no
> runtime dependencies on any GCC components on Linux? If not, will this
> ever be possible?
We are working on a new libc++abi: http://libcxxabi.llvm.org/ which carries the llvm license.
Howard
2012 May 05
1
[LLVMdev] lld file format as native OS executable format
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
2012 May 02
0
[LLVMdev] lld file format as native OS executable format
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
2011 Oct 20
4
[LLVMdev] LLVM Language Reference Strictness
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
2012 May 02
4
[LLVMdev] lld file format as native OS executable format
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.
2011 Oct 20
0
[LLVMdev] LLVM Language Reference Strictness
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
>
2011 Oct 20
3
[LLVMdev] LLVM Language Reference Strictness
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
2011 Oct 20
0
[LLVMdev] LLVM Language Reference Strictness
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
2011 Oct 20
1
[LLVMdev] Missing Configure Checks
>
> 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
2016 Oct 26
1
Segfault in llc 3.8.0 building GHC
I found a fix! The first hunk of https://reviews.llvm.org/D17533
(lib/CodeGen/TargetFrameLoweringImpl.cpp) on top of 3.8.1 does the
trick.
Does llvm do patch releases of old versions?
Davide Italiano <davide at freebsd.org> writes:
> On Fri, Oct 21, 2016 at 6:19 AM, Shea Levy via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
>> Hi all,
>>
>> I'm hitting
2012 May 02
0
[LLVMdev] lld file format as native OS executable format
On 5/2/12 10:29 AM, Shea Levy wrote:
> 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?
By lld, do you mean the LLVM IR bitcode format, or are you referring to
something else?
As far as using LLVM IR as a format for executables, there
2011 Oct 20
2
[LLVMdev] Missing Configure Checks
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
2014 Feb 14
5
[LLVMdev] [llvm] r201432 - Remove myself as owner of libc++
On Feb 14, 2014, at 1:09 PM, Howard Hinnant <hhinnant at apple.com> wrote:
> Author: hhinnant
> Date: Fri Feb 14 15:09:01 2014
> New Revision: 201432
>
> URL: http://llvm.org/viewvc/llvm-project?rev=201432&view=rev
> Log: Remove myself as owner of libc++
>
> Modified:
> llvm/trunk/CODE_OWNERS.TXT
>
> Modified: llvm/trunk/CODE_OWNERS.TXT
> URL:
2016 Oct 21
3
Segfault in llc 3.8.0 building GHC
Hi all,
I'm hitting a segfault in llc when trying to build GHC:
http://sprunge.us/ZVGB. What is the best way to debug this? I'm able to
bump to 3.8.1 if needed, but GHC tends to break when updating major
versions due to IR incompatibilities.
Thanks,
Shea
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size:
2014 Feb 14
3
[LLVMdev] [cfe-dev] [llvm] r201432 - Remove myself as owner of libc++
On Fri, Feb 14, 2014 at 1:29 PM, Howard Hinnant <hhinnant at apple.com> wrote:
> On Feb 14, 2014, at 4:23 PM, Marshall Clow <mclow.lists at gmail.com> wrote:
>
>> On Feb 14, 2014, at 1:09 PM, Howard Hinnant <hhinnant at apple.com> wrote:
>>
>>> Author: hhinnant
>>> Date: Fri Feb 14 15:09:01 2014
>>> New Revision: 201432
>>>
2013 Feb 25
1
Per-driver Disk Image Type Support
Hello,
Where can I find documentation about which formats for disk images each
driver supports? In particular, do they all support raw disk images?
Thanks,
Shea Levy
2012 Mar 20
1
Macbook Pro 5,3 Video Issues
Hello,
On my system (Linux 3.3, booting in EFI mode, using Nouveau with
nouveau.noaccel=1 due to
https://bugs.freedesktop.org/show_bug.cgi?id=27501 ), I can't figure out
how to change the backlight or switch which of the two graphics cards (I
have an Nvidia 9600M GT and a 9400M, both are recognized by nouveau but
only the 9400M is ever used) Linux uses for the framebuffer or X uses
for
2011 Oct 20
0
[LLVMdev] Missing Configure Checks
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 case
> someone more experienced
2011 Oct 20
0
[LLVMdev] LLVM Language Reference Strictness
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