search for: yasskin

mike-m, is there any way to configure doxygen to produce human-readable anchors? They might have avoided the duplication on this thread, since Erick and John could have seen that I was linking to their suggestions. On Fri, May 7, 2010 at 8:47 PM, Jeffrey Yasskin <jyasskin at google.com> wrote: > Try http://llvm.org/doxygen/classllvm_1_1ConstantExpr.html#a2ea738dfa37ea93c71756be89ba8d92 > or http://llvm.org/doxygen/classllvm_1_1TargetData.html#64c154a7844026e76e18f792ee4ad4b3 > > On Fri, May 7, 2010 at 8:26 PM, Gang.Yao <ttoole9 at gmai...

No anchor naming options that I can find. But I'll keep an eye out for things that may improve anchor readability. --mike-m On 2010-05-08, at 12:53 PM, Jeffrey Yasskin wrote: > mike-m, is there any way to configure doxygen to produce > human-readable anchors? They might have avoided the duplication on > this thread, since Erick and John could have seen that I was linking > to their suggestions. > > On Fri, May 7, 2010 at 8:47 PM, Jeffrey Yassk...

Jeffrey Yasskin wrote: > We currently use two different techniques to get whole libraries > included into the .so. On Linux (gnu ld and gold), we pass > --whole-archive, while on OSX we pass -all_load. Which ld does FreeBSD > use? If you can rearrange tools/llvm-shlib/Makefile until it works for > y...

...es are local to the RecordingJITEventListener, since the + // JITEventListener interface makes no guarantees about the order of + // calls between Listeners. + int Index; Use "unsigned" instead of "int"? Can index ever be negative? Evan On Jun 24, 2009, at 1:26 PM, Jeffrey Yasskin wrote: > Ack, sorry. I should have sent this to llvm-commits instead. :-P > Followups there please. > > On Wed, Jun 24, 2009 at 12:02 PM, Jeffrey > Yasskin<jyasskin at google.com> wrote: >> I intend to use this to support oprofile's ability to symbolize >>...

On 2009-11-01 08:40, Jeffrey Yasskin wrote: > 2009/10/30 Török Edwin <edwintorok at gmail.com>: > >> On 2009-10-29 23:55, Jeffrey Yasskin wrote: >> >>> On Thu, Oct 29, 2009 at 2:30 PM, Nicolas Geoffray >>> <nicolas.geoffray at lip6.fr> wrote: >>> >>> >...

In r85295, in response to the discussion at http://llvm.org/PR5184 (Lazy JIT ain't thread-safe), I changed the default JIT from lazy to non-lazy. It has since come to my attention that this may have been the wrong change, so I wanted to ask you guys. A couple reasons to make the default non-lazy compilation: * The lack of thread-safety surprises new users * Crashes due to this will be rare

...the > +  // JITEventListener interface makes no guarantees about the order of > +  // calls between Listeners. > +  int Index; > > Use "unsigned" instead of "int"? Can index ever be negative? Sure, it's unsigned now. > On Jun 24, 2009, at 1:26 PM, Jeffrey Yasskin wrote: > >> Ack, sorry. I should have sent this to llvm-commits instead. :-P >> Followups there please. >> >> On Wed, Jun 24, 2009 at 12:02 PM, Jeffrey >> Yasskin<jyasskin at google.com> wrote: >>> I intend to use this to support oprofile's abilit...

Good catch! I meant "for iterator" of course. Attached is a corrected patch together with an old patch for clang just to keep them together. Could someone commit these, please? Thanks, Victor 2009/11/4 Jeffrey Yasskin <jyasskin at google.com> > + // Otherwise this is a copy constructor for const_iterator. > > Do you mean "for iterator"? > > Otherwise, looks good to me. If you can commit this, please do. > Otherwise, someone else should as I'm not going to be around tomorro...

I have no objection to Chris' proposal. Evan On Oct 29, 2009, at 9:45 AM, Jeffrey Yasskin wrote: > Are you objecting to Chris's proposal? I was waiting to implement it > until you replied so I wouldn't have to implement two things. I > disagree with a lot of what you wrote below, but it's not worth > arguing about if there's a compromise we can both live wit...

On 2009-10-29 23:55, Jeffrey Yasskin wrote: > On Thu, Oct 29, 2009 at 2:30 PM, Nicolas Geoffray > <nicolas.geoffray at lip6.fr> wrote: > >> Hi Jeffrey, >> >> Jeffrey Yasskin wrote: >> >>> Cool, I'll start implementing it. >>> >>> >> Great! Thank...

...hat having a default that's right in nearly all cases is the best option (the only concrete counter-example I've seen is lli), but I'm happy to write another patch with a global forced choice or commit this one if that's what you guys want. On Thu, Oct 29, 2009 at 11:46 AM, Jeffrey Yasskin <jyasskin at google.com> wrote: > Cool, I'll start implementing it. > > Thanks all for the decision! > > On Thu, Oct 29, 2009 at 11:03 AM, Evan Cheng <evan.cheng at apple.com> wrote: >> I have no objection to Chris' proposal. >> >> Evan >>...

Cool, I'll start implementing it. Thanks all for the decision! On Thu, Oct 29, 2009 at 11:03 AM, Evan Cheng <evan.cheng at apple.com> wrote: > I have no objection to Chris' proposal. > > Evan > > On Oct 29, 2009, at 9:45 AM, Jeffrey Yasskin wrote: > >> Are you objecting to Chris's proposal? I was waiting to implement it >> until you replied so I wouldn't have to implement two things. I >> disagree with a lot of what you wrote below, but it's not worth >> arguing about if there's a compromise...

Hi Jeffrey, Jeffrey Yasskin wrote: > Cool, I'll start implementing it. > Great! Thanks. Just to clarify things: on my end, it doesn't really matter what is the default behavior, as long as vmkit can continue to have the existing behavior of lazy compilation. With Chris' solution, I was wondering how...

On Fri, Apr 16, 2010 at 9:30 PM, Jeffrey Yasskin <jyasskin at google.com> wrote: > On Sun, Apr 11, 2010 at 10:07 PM, Jeffrey Yasskin <jyasskin at google.com> wrote: >> I'll forward your next draft back to the stackless folks, unless you >> want to pick up the thread with them. > > Their reply: http://thread.gm...

What does nsw nuw do? Micah -----Original Message----- From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Dan Gohman Sent: Tuesday, October 13, 2009 10:06 AM To: Jeffrey Yasskin Cc: LLVM Developers Mailing List Subject: Re: [LLVMdev] 65bit integer math On Oct 12, 2009, at 9:42 PM, Jeffrey Yasskin wrote: > On Mon, Oct 12, 2009 at 8:22 PM, Eli Friedman > <eli.friedman at gmail.com> wrote: >> On Mon, Oct 12, 2009 at 6:15 PM, Villmow, Micah <Micah.Vil...

...note that: $ file /opt/clang+llvm-2.7-i386-darwin10/bin/llvm-as /opt/clang+llvm-2.7-i386-darwin10/bin/llvm-as: Mach-O 64-bit executable x86_64 Why's the i386 package have an x86_64 binary in it? That could explain why it doesn't work on darwin9. On Fri, Mar 19, 2010 at 9:49 AM, Jeffrey Yasskin <jyasskin at google.com> wrote: > Hi Tanya, > > On darwin9, the binaries in the darwin10 packages give: > > $  /opt/clang+llvm-2.7-i386-darwin10/bin/llvm-as --help > dyld: unknown required load command 0x80000022 > Trace/BPT trap > > That could be unavoidable, of co...

On Wed, Apr 28, 2010 at 10:48 AM, Yuri <yuri at tsoft.com> wrote: > Jeffrey Yasskin wrote: >> >> We currently use two different techniques to get whole libraries >> included into the .so. On Linux (gnu ld and gold), we pass >> --whole-archive, while on OSX we pass -all_load. Which ld does FreeBSD >> use? If you can rearrange tools/llvm-shlib/Makefile...

On Wed, Jul 21, 2010 at 9:50 AM, Jeffrey Yasskin <jyasskin at google.com> wrote: >> This (Unknown constant! in bitcode writer when -g is used) is a known >> bug in CloneModule, because it is not cloning MDNodes appropriately. > > What's the link to the bug report? Are you fixing it? PR 7689. Fixed in r109117. - Devang

2009/10/30 Török Edwin <edwintorok at gmail.com>: > On 2009-10-29 23:55, Jeffrey Yasskin wrote: >> On Thu, Oct 29, 2009 at 2:30 PM, Nicolas Geoffray >> <nicolas.geoffray at lip6.fr> wrote: >> >>> Hi Jeffrey, >>> >>> Jeffrey Yasskin wrote: >>> >>>> Cool, I'll start implementing it. >>>> >>>&...

...victor.zverovich at googlemail.com> > Good catch! I meant "for iterator" of course. Attached is a corrected patch > together with an old patch for clang just to keep them together. > Could someone commit these, please? > > Thanks, > Victor > > 2009/11/4 Jeffrey Yasskin <jyasskin at google.com> > > + // Otherwise this is a copy constructor for const_iterator. >> >> Do you mean "for iterator"? >> >> Otherwise, looks good to me. If you can commit this, please do. >> Otherwise, someone else should as I'm not go...