similar to: [LLVMdev] RFC: Darwin EH Patch

Displaying 20 results from an estimated 30000 matches similar to: "[LLVMdev] RFC: Darwin EH Patch"

2007 Sep 11
0
[LLVMdev] RFC: Darwin EH Patch
Hi Anton, >> It's not exactly tweaking magic knobs. It's doing something that's >> already done -- putting the information in the TAI object, and >> allowing the specific back-end to set the appropriate strings. > It seems to me, that simple strings / bools there are not enough :) > "$non_lazy_ptr" emission is already in asm printers (in 2 places!).
2007 Sep 11
2
[LLVMdev] RFC: Darwin EH Patch
Hello, Bill. > It's not exactly tweaking magic knobs. It's doing something that's > already done -- putting the information in the TAI object, and > allowing the specific back-end to set the appropriate strings. It seems to me, that simple strings / bools there are not enough :) "$non_lazy_ptr" emission is already in asm printers (in 2 places!). The
2007 Sep 11
1
[LLVMdev] RFC: Darwin EH Patch
Hello, Bill > Comments? I don't personally like this patch. It seems, that emitted data encoding is linker (=subtarget) specific. For example, gcc uses three different data encodings to emit dwarf data on darwin. I think we should introduce subtarget hooks for encoding selection of data being emitted (there is already one: needSet / *AbsoluteOffsets etc). Also "generic" function
2011 Aug 02
2
[LLVMdev] RFC: Exception Handling Rewrite
On Jul 31, 2011, at 11:06 AM, Duncan Sands wrote: >> //===-------------------------- >> // The 'landingpad' Instruction >> // >> >> The 'landingpad' instruction replaces the current 'llvm.eh.exception' and >> 'llvm.eh.selector' intrinsics. >> >> // Syntax: >> >> %res = landingpad<somety>
2007 Aug 24
3
[LLVMdev] Turning on exception handling codegen
On 8/24/07, Chris Lattner <sabre at nondot.org> wrote: > > so how about turning it on? > > It sounds good, but I'm concerned about darwin/x86. Bill, can you see how > well darwin/x86 is doing these days? If there are no regressions from > turning this on by default, we should do it. :) > I'm assuming that this is 4.2? :-) I'll give it a try. -bw
2007 Sep 11
0
[LLVMdev] RFC: Darwin EH Patch
And now the patch. :-) -bw -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: eh-diff.txt URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20070910/015f3c21/attachment.txt>
2007 Aug 24
0
[LLVMdev] Turning on exception handling codegen
On 8/24/07, Bill Wendling <isanbard at gmail.com> wrote: > On 8/24/07, Chris Lattner <sabre at nondot.org> wrote: > > > so how about turning it on? > > > > It sounds good, but I'm concerned about darwin/x86. Bill, can you see how > > well darwin/x86 is doing these days? If there are no regressions from > > turning this on by default, we should
2013 Oct 12
0
[LLVMdev] "target-features" and "target-cpu" attributes
FYI: http://lists.cs.uiuc.edu/pipermail/llvmdev/2013-October/066389.html Please read and let me know you comments. -bw On Oct 11, 2013, at 2:47 PM, Dmitry Babokin <babokin at gmail.com> wrote: > Looking forward to these changes! Thanks for working on it. > > > On Fri, Oct 11, 2013 at 10:32 PM, Bill Wendling <isanbard at gmail.com> wrote: > Hi Dmitry, > > I
2013 Oct 11
2
[LLVMdev] "target-features" and "target-cpu" attributes
Looking forward to these changes! Thanks for working on it. On Fri, Oct 11, 2013 at 10:32 PM, Bill Wendling <isanbard at gmail.com> wrote: > Hi Dmitry, > > I can try my best, but it would be a bit tricky to get it all finished by > then... > > -bw > > On Oct 11, 2013, at 4:10 AM, Dmitry Babokin <babokin at gmail.com> wrote: > > Bill, > > Are there
2009 May 08
3
[LLVMdev] RFA: flag_objc_abi on Non-Darwin Platforms?
Is the flag_objc_abi variable available on non-Darwin platforms in llvm-gcc? I want to use it in llvm-backend.cpp to conditionalize a test. But I don't want to break Linux, Ada, Fortran, etc. -bw
2007 Sep 25
2
[LLVMdev] Compilation Failure
On 9/25/07, Daniel Berlin <dberlin at dberlin.org> wrote: > On 9/24/07, Bill Wendling <isanbard at gmail.com> wrote: > > On Sep 24, 2007, at 3:15 PM, Dale Johannesen wrote: > > > > Weird. I see a potential problem, though. The code is like this: > > > > void dumpToDOUT(SparseBitVector<> *bitmap) { > > dump(*bitmap, DOUT); > > } >
2013 Oct 11
0
[LLVMdev] "target-features" and "target-cpu" attributes
Hi Dmitry, I can try my best, but it would be a bit tricky to get it all finished by then... -bw On Oct 11, 2013, at 4:10 AM, Dmitry Babokin <babokin at gmail.com> wrote: > Bill, > > Are there any chances that you complete it before 3.4 is branched? > > > On Thu, Oct 10, 2013 at 10:16 PM, Bill Wendling <isanbard at gmail.com> wrote: > On Oct 10, 2013, at
2013 Oct 11
2
[LLVMdev] "target-features" and "target-cpu" attributes
Bill, Are there any chances that you complete it before 3.4 is branched? On Thu, Oct 10, 2013 at 10:16 PM, Bill Wendling <isanbard at gmail.com> wrote: > On Oct 10, 2013, at 4:22 AM, Dmitry Babokin <babokin at gmail.com> wrote: > > > Bill, > > > > Thanks for answering. To make sure that we are on the same page, let's > agree on definitions :) Here, by
2009 Jan 27
2
[LLVMdev] RFC: -fwritable-strings Change
On Tue, Jan 27, 2009 at 1:15 PM, Eli Friedman <eli.friedman at gmail.com> wrote: > On Tue, Jan 27, 2009 at 1:00 PM, Bill Wendling <isanbard at gmail.com> wrote: >> Even with C code, we place a null string in a writable >> section, which isn't correct. > > You could say that, but it's not really wrong... say you had a 10 > kilobyte struct that was all
2007 Sep 25
0
[LLVMdev] Compilation Failure
On 9/24/07, Bill Wendling <isanbard at gmail.com> wrote: > On Sep 24, 2007, at 3:15 PM, Dale Johannesen wrote: > > > > > On Sep 24, 2007, at 3:07 PM, Bill Wendling wrote: > > > >> A debug or release build? > >> > >> -bw > > > > Both, actually. > > Weird. I see a potential problem, though. The code is like this: > >
2009 Jun 16
0
[LLVMdev] PIC documentation ?
>> 2. ABI docs for Darwin (x86, x86_64, ppc, ppc64) you might find >> somewhere @apple.com. There you can have all 3 types of PIC code: >> static (no pic at all), DynamicNoPIC and full PIC. > > Okay. We need documentation, what is the difference between > DynamicNoPIC and > full PIC ? The best way to figure this out is to run a small program through and look at
2015 Jan 05
2
[LLVMdev] LTO v. opt
On Jan 3, 2015, at 11:52 PM, Bill Wendling <isanbard at gmail.com> wrote: > On Jan 2, 2015, at 8:32 PM, David Callahan <dcallahan at fb.com> wrote: > >> Hi, >> >> I am new to the LLVM dev community so forgive a perhaps obvious question. I am looking at bug 17623 which is an LTO/optimizer interaction bug. I am working on a Mac with Xcode installed but have
2011 Jul 23
14
[LLVMdev] RFC: Exception Handling Rewrite
What? Yet another EH proposal?! This one is different from the others in that I'm planning to start implementing this shortly. But I want your feedback! I've all ready gotten a lot of feedback from Chris, John, Jim, Eric, and many others. Now is your turn! Please read this proposal and send me your comments, suggestions, and concerns. -bw
2006 Apr 16
0
[LLVMdev] 1.7 Pre-Release Ready for Testing
Hi Tanya, Attached are the "make check" results from my machine Darwin Bill-Wendlings-Computer.local 8.6.0 Darwin Kernel Version 8.6.0: Tue Mar 7 16:58:48 PST 2006; root:xnu-792.6.70.obj~1/RELEASE_PPC Power Macintosh powerpc I'll have the llvm-test results available later. -bw -------------- next part -------------- A non-text attachment was scrubbed... Name: check.out Type:
2011 Oct 18
1
[LLVMdev] Building LLVM on PPC
Please don't be alarmed by the failed compiles on llvm-ppc-darwin. They are likely not your fault. I'm trying to get a PPC build bot setup (arxan_bellini), and so far it's dying here: Linking CXX shared library ../../lib/libgtest.dylib Undefined symbols: "vtable for llvm::raw_ostream", referenced from: __ZTVN4llvm11raw_ostreamE$non_lazy_ptr in gtest.cc.o