similar to: [LLVMdev] Two suggestions for improving LLVM error reporting

Displaying 20 results from an estimated 10000 matches similar to: "[LLVMdev] Two suggestions for improving LLVM error reporting"

2010 Jan 09
0
[LLVMdev] Two suggestions for improving LLVM error reporting
On Jan 7, 2010, at 3:52 PM, Talin wrote: > I realize that LLVM assertion results aren't intended to be seen by end-users ever - they are there to tell front-end developers that they screwed up. Even so, I can think of two things that would make it easier for front-end developers to track down what they did wrong without having to jump into the debugger: Ok. > 1) Be able to set a
2010 Jan 09
3
[LLVMdev] Two suggestions for improving LLVM error reporting
On Saturday 09 January 2010 06:11:03 Chris Lattner wrote: > My eventual goal (perhaps for LLVM 3.0) is to eliminate our current > structural type system altogether. The benefits are blown away by the > costs, eventually we should just fix this design mistake. In the meantime, > I'm not opposed to adding a Module* to VMCore that type dumping defaults to > if non-null. Can you
2010 Jan 09
0
[LLVMdev] Two suggestions for improving LLVM error reporting
On Sat, Jan 9, 2010 at 9:27 AM, Kenneth Uildriks <kennethuil at gmail.com> wrote: > On Sat, Jan 9, 2010 at 1:09 AM, Chris Lattner <clattner at apple.com> wrote: >> >> On Jan 9, 2010, at 12:07 AM, Jon Harrop wrote: >> >>> On Saturday 09 January 2010 06:11:03 Chris Lattner wrote: >>>> My eventual goal (perhaps for LLVM 3.0) is to eliminate our
2008 Apr 04
1
java-1.6.0-openjdk packages for testing
Johnny, Thought I'd try these out for you. Looks like a prerequisite is missing? yum --enablerepo=c5-testing install java-1.6.0-openjdk\* <snip the usual gobbledygook> 330 packages excluded due to repository priority protections Parsing package install arguments Resolving Dependencies --> Populating transaction set with selected packages. Please wait. ---> Package
2009 Jul 15
3
[LLVMdev] LLVMContext: Suggestions for API Changes
Owen Anderson wrote: > On Jul 15, 2009, at 7:44 AM, John Criswell wrote: > >> 1) If technically possible, add the new API first, get it working, >> email >> llvmdev describing the old and new APIs, provide some lead time for >> people to change over, and then remove the old APIs. This makes it >> easier to plan when I fix problems due to LLVM API changes
2009 Jul 15
1
[LLVMdev] LLVMContext: Suggestions for API Changes
Owen Anderson wrote: > > On Jul 15, 2009, at 9:53 AM, John Criswell wrote: > >> Owen Anderson wrote: >>> On Jul 15, 2009, at 7:44 AM, John Criswell wrote: >>> >>>> 1) If technically possible, add the new API first, get it working, >>>> email >>>> llvmdev describing the old and new APIs, provide some lead time for
2009 Jul 15
0
[LLVMdev] LLVMContext: Suggestions for API Changes
On Wed, Jul 15, 2009 at 2:24 PM, Albert Graef<Dr.Graef at t-online.de> wrote: > Owen Anderson wrote: >> On Jul 15, 2009, at 10:56 AM, Jean-Daniel Dupas wrote: >>> >>> You mean like this subject ? >>> >>> http://lists.cs.uiuc.edu/pipermail/llvmdev/2009-June/023505.html >> >> Notice the sender line on that email... ;-) > > Yes, you
2009 Jul 15
0
[LLVMdev] LLVMContext: Suggestions for API Changes
On Jul 15, 2009, at 7:44 AM, John Criswell wrote: > 1) If technically possible, add the new API first, get it working, > email > llvmdev describing the old and new APIs, provide some lead time for > people to change over, and then remove the old APIs. This makes it > easier to plan when I fix problems due to LLVM API changes and when I > can work on our own bugs. :) The
2009 Jul 15
2
[LLVMdev] LLVMContext: Suggestions for API Changes
Le 15 juil. 09 à 19:07, Owen Anderson a écrit : > > On Jul 15, 2009, at 9:53 AM, John Criswell wrote: > >> Owen Anderson wrote: >>> On Jul 15, 2009, at 7:44 AM, John Criswell wrote: >>> >>>> 1) If technically possible, add the new API first, get it working, >>>> email >>>> llvmdev describing the old and new APIs, provide some
2009 Jul 15
0
[LLVMdev] LLVMContext: Suggestions for API Changes
On Jul 15, 2009, at 9:53 AM, John Criswell wrote: > Owen Anderson wrote: >> On Jul 15, 2009, at 7:44 AM, John Criswell wrote: >> >>> 1) If technically possible, add the new API first, get it working, >>> email >>> llvmdev describing the old and new APIs, provide some lead time for >>> people to change over, and then remove the old APIs. This
2012 Apr 23
1
[LLVMdev] Problem about the type of Function's arguement in llvm
I read the tutorial doc and some info of SSA, finally understand it. Thanks for your help. And the segmentation error of loading arguementation occurs, (gdb error info) Program received signal SIGSEGV, Segmentation fault. 0x0855bb68 in llvm::LoadInst::LoadInst(llvm::Value*, char const*, bool, llvm::Instruction*) () code is like follows: //#include necessary header files int main(){
2006 Sep 21
9
problem with TextCtrl#get_insertion_point
I''m trying to un-ignore TextCtrl#get_selection. The typemaps work fine, but in the process it breaks get_insertion_point. This is because (on Mac, tho not GTK), get_insertion_point calls get_selection internally and simply returns the first value. I think the return value is being converted from a long to a ruby int twice, because when get_selection is wrapped, it works fine but the
2017 Oct 14
2
Bug in replaceUsesOfWith: does not keep addrspace consistent in GEP
Hello, Calling `replaceUsesOfWith` with a value in a different addrspace does not keep the addrspace of a GEP consistent. Is this known? Is this a bug or expected behaviour? Minimal counterexample link <https://gist.github.com/bollu/152ba5e1c20c03c7fc6d8c7b23ba828f> Reproduced here: #include <iostream> #include "llvm/ADT/APFloat.h" #include
2009 Jul 15
2
[LLVMdev] LLVMContext: Suggestions for API Changes
Dear LLVMers, LLVM is currently undergoing a change in its programming API, most of which has to do with the transition to using an LLVMContext. I've been trying to keep two LLVM projects, poolalloc and SAFECode, up-to-date with LLVM mainline, but it has become frustrating because: 1) The API changes occur frequently. Each morning I come in and have to fix something because the API
2018 Sep 16
2
LLVMContext: Threads and Ownership.
Agreed, the existing ownership seems sub-optimal. I wouldn't say broken, but subtle at least - looks like you get the choice to either manage the ownership of the Module object yourself, or let the context handle it (eg: currently it'd be valid to just do "{ LLVMContext C; new Module(C); new Module(C); }" - Modules end up owned by the context and cleaned up there). Might be hard
2018 Sep 16
2
LLVMContext: Threads and Ownership.
In the most basic case, I'd imagine something like this: auto C = std::make_shared<LLVMContext>(); struct ModuleAndSharedContextDeleter { std::shared_ptr<LLVMContext> C; operator()(Module *M) { delete M; } /* ctor to init C */}; std::unique_ptr<Module, ModuleAndSharedDeleter> M(new Module(C.get()), ModuleAndSharedContextDeleter(C)); (or invert this and traffic in structs
2012 Sep 13
5
[LLVMdev] Fail to compile LLVM on Gentoo Linux
Hi all, I think it's Gentoo's bug, but I want to know if anyone has the same issue here. I am compiling LLVM trunk on Gentoo (gcc 4.5.2), and I get error message below, --- make[4]: Entering directory `/nfs_home/chenwj/llvm-3.1/svn/build/tools/clang/lib/Frontend' llvm[4]: Compiling InitHeaderSearch.cpp for Release+Asserts build
2004 Apr 12
3
Decoding with 8 bit-samples
Hi! I'd like to make a stereo 8-bit wav file from a stereo (16 bit) ogg vorbis file (in delphi, with the vorbisfile). I use: ret := ov_open_callbacks(filein,vf,nil,0,ops_callbacks); if ret = 0 Then begin fileOut := TFileStream.Create(savedlg.FileName,fmCreate); repeat ret := ov_read(VF, pcmout, BufferSize, 0, 1, 1, nil); //'cause of the 8-bit
2009 Aug 07
3
Anyone had any luck with SIP clients on the iPhone platform?
Hi, I've tried two SIP clients so far and both have unusable outgoing audio quality. Skype app sounds fine, and recording the same mic sounds fine, so I can only assume there is an issue with the clients themselves. Both clients allow you to register and make calls via SIP with any abitrary provider and credentials, so they'll work with Asterisk. I've tried them with two good
2009 Jun 09
2
Sweave and accents
Hello. I want to write my notes in Sweave in my own language (spanish). But my language has accents and when I run Sweave in R to translate my Snw file into the tex file the accents are translated into unrecognizable characters. For example, the word "cami?n" (truck) is translated into "cami??n" Somebody knows how can I do it? One solution I don't like is using a