search for: daniel_dunbar

On Sat, Jul 8, 2017 at 10:07 AM Daniel Dunbar <daniel_dunbar at apple.com> wrote: > > > On Jul 8, 2017, at 7:32 AM, David Blaikie <dblaikie at gmail.com> wrote: > > Ideally/the better integration with Buildbot would be to have these > outputs referenced as "associated files" (it's been a while since I played > wit...

...----- > > Message: 1 > Date: Fri, 25 Jan 2013 14:18:08 -0800 > From: Daniel Dunbar <daniel at zuster.org> > To: Sebastian Pop <spop at codeaurora.org> > Cc: "cfe-dev at cs.uiuc.edu Developers" <cfe-dev at cs.uiuc.edu>, Daniel > Dunbar <daniel_dunbar at apple.com>, LLVM Developers Mailing > List > <llvmdev at cs.uiuc.edu> > Subject: Re: [LLVMdev] [cfe-dev] RFC: put commit messages in *-commits > subject lines? > Message-ID: > < > CAEU8z69eX+QQyakoKMK38fGZ9ZN5xOQV_tq+HhxGromLOAmsXg a...

...about having an environment variable FILECHECKER_VERBOSE=1? > This would not require substitutions, and could be even set automatically > by “lit” when launched with “-v”. > At least to me that would make debugging tests much easier. > > On Jul 7, 2017, at 3:05 PM, Daniel Dunbar <daniel_dunbar at apple.com> wrote: > > > On Jul 7, 2017, at 2:19 PM, Reid Kleckner <rnk at google.com> wrote: > > On Fri, Jul 7, 2017 at 1:20 PM, George Karpenkov via llvm-dev < > llvm-dev at lists.llvm.org> wrote: >> >> Thus, I propose modifying FileCheck default beh...

> On Jul 7, 2017, at 2:19 PM, Reid Kleckner <rnk at google.com> wrote: > > On Fri, Jul 7, 2017 at 1:20 PM, George Karpenkov via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: > Thus, I propose modifying FileCheck default behavior to dump all swallowed output on stderr when the test has failed. > Would there be any objections to

...and re-implement them in JITObjectWriter ? This is my current solution but I fear it's not so good for the performances. - Make a JIT_raw_ostream (or a memory_raw_ostream) class (inherits from raw_ostream). What do you think ? Olivier. On Fri, Apr 16, 2010 at 10:58 PM, Daniel Dunbar <daniel_dunbar at apple.com>wrote: > I do have an opinion, but don't have enough time to comment in much depth. > The approximate approach I had in mind sounds like what you describe, > though, the JITObjectWriter is the core piece, the other pieces probably > fall into place as it becomes obv...

I do have an opinion, but don't have enough time to comment in much depth. The approximate approach I had in mind sounds like what you describe, though, the JITObjectWriter is the core piece, the other pieces probably fall into place as it becomes obvious if they are needed. It should be pretty straightforward to bring up something which works for running code with no external symbols, if you

On Aug 7, 2012, at 3:08 PM, Eli Friedman wrote: > On Tue, Aug 7, 2012 at 2:59 PM, Chad Rosier <mcrosier at apple.com> wrote: >> All, >> I would like to propose a fairly significant change to the unused argument warning (i.e., removing it for the most part), but wanted to get some feedback before investing a great deal of time. In my opinion, the implementation of this

I thought it was already fixed, so no. I hate to say this, but can you try first: touch $LLVM_SRC_ROOT/LLVMBuild.txt and a make? If that doesn't work, try a make clean? I'll try and find a real fix tomorrow. - Daniel On Dec 12, 2011, at 5:44 PM, Evan Cheng wrote: > I'm hitting this. Is there ETA for the fix? > > Evan > > On Dec 12, 2011, at 2:58 PM, Daniel

On Dec 12, 2011, at 2:51 PM, Tony Linthicum wrote: > On 12/12/2011 4:49 PM, Eric Christopher wrote: >> >> >> On Dec 12, 2011, at 2:41 PM, Eric Christopher wrote: >> >>> >>> On Dec 12, 2011, at 2:36 PM, Tony Linthicum wrote: >>> >>>> On 12/12/2011 4:28 PM, Jakob Stoklund Olesen wrote: >>>>> >>>>>