similar to: [LLVMdev] Export maps and -fvisibility-inlines-hidden

Displaying 20 results from an estimated 500 matches similar to: "[LLVMdev] Export maps and -fvisibility-inlines-hidden"

2004 Mar 05
1
Slow reshape from 5x600000 to 6311 x 132
I have a dataset that's a few hundred thousand rows from a database (read in via dbreadTable). The database is like: > str(measures) `data.frame': 609363 obs. of 5 variables: $ vih.id : int 1 2 3 4 5 6 7 8 9 10 ... $ vi.id : int 1 2 3 4 5 6 7 8 9 10 ... $ vih.value: chr "0" "1989" "0" "N/A" ... $ vih.date : chr
2012 Mar 15
1
eigenvalues of matrices of partial derivatives with ryacas
Hello, I am trying to construct two matrices, F and V, composed of partial derivatives and then find the eigenvalues of F*Inverse(V). I have the following equations in ryacas notation: > library(Ryacas) > FIh <- Expr("betah*Sh*Iv") > FIv <- Expr("betav*Sv*Ih") > VIh <- Expr("(muh + gamma)*Ih") > VIv <- Expr("muv*Iv") I
2009 Aug 28
3
[LLVMdev] Regular Expression lib support
Nice! This looks good to me but probably Chris or someone else should sign off on it. There were two minor warnings on Darwin: -- In file included from /Volumes/Data/Users/ddunbar/llvm/lib/Support/regexec.c:81: /Volumes/Data/Users/ddunbar/llvm/lib/Support/regengine.inc: In function 'sbackref': /Volumes/Data/Users/ddunbar/llvm/lib/Support/regengine.inc:665: warning: control reaches end of
2009 Aug 05
0
[LLVMdev] Profiling in LLVM Patch Followup 1
Hi Andreas, Sorry for the lag time... On Wed, Jul 22, 2009 at 5:47 AM, Andreas Neustifter<e0325716 at student.tuwien.ac.at> wrote: > Hi Daniel! > > Daniel Dunbar wrote: >> I merged in my changes to your patch, which results in the attached >> patch. There may be some missed merge errors. The main problem I have >> with the rest of this patch is that it causes a
2009 Jul 23
0
[LLVMdev] Profiling in LLVM Patch Followup 1
Good Morning. On 22.07.09 14:47), Andreas Neustifter wrote: > Daniel Dunbar wrote: >> I merged in my changes to your patch, which results in the attached >> patch. There may be some missed merge errors. The main problem I have >> with the rest of this patch is that it causes a regression in >> llvm-prof's behavior. I tried running edge profiling on the >>
2009 Jul 23
1
[LLVMdev] Profiling in LLVM Patch Followup 1
Sorry, forgot attachment. On 23.07.09 07:40), Andreas Neustifter wrote: > Good Morning. > > On 22.07.09 14:47), Andreas Neustifter wrote: >> Daniel Dunbar wrote: >>> I merged in my changes to your patch, which results in the attached >>> patch. There may be some missed merge errors. The main problem I have >>> with the rest of this patch is that it
2009 Oct 16
1
[LLVMdev] Command Line Bugzilla
Hi all, Thought this might be of general interest, I hacked up the pybugz tool to work with llvm.org. It's here if you want it: http://t1.minormatter.com/~ddunbar/pybugz-llvm-0.7.3.tgz Unpack somewhere, and make a link to the 'bugz' script. Usage: -- ddunbar at ozzy-2:~$ bugz get 1000 * Using http://llvm.org/bugs/ * Getting bug 1000 .. Title : Chris Is Buggy Assignee :
2009 Aug 05
2
[LLVMdev] Profiling in LLVM Patch Followup 1
Hi! Daniel Dunbar wrote: > > Sorry for the lag time... No problem. As long as I know that you get to it sometime its fine for me... > On Wed, Jul 22, 2009 at 5:47 AM, Andreas > Neustifter<e0325716 at student.tuwien.ac.at> wrote: >> Hi Daniel! >> >> Daniel Dunbar wrote: >>> I merged in my changes to your patch, which results in the attached
2009 Aug 05
0
[LLVMdev] Profiling in LLVM Patch Followup 1
On Wed, Aug 5, 2009 at 12:22 PM, Andreas Neustifter<e0325716 at student.tuwien.ac.at> wrote: >> On Wed, Jul 22, 2009 at 5:47 AM, Andreas >> Neustifter<e0325716 at student.tuwien.ac.at> wrote: >>> >>> Hi Daniel! >>> >>> Daniel Dunbar wrote: >>>> >>>> I merged in my changes to your patch, which results in the
2009 Jul 22
4
[LLVMdev] Profiling in LLVM Patch Followup 1
Hi Daniel! Daniel Dunbar wrote: > I merged in my changes to your patch, which results in the attached > patch. There may be some missed merge errors. The main problem I have > with the rest of this patch is that it causes a regression in > llvm-prof's behavior. I tried running edge profiling on the > MultiSource/Applications/aha benchmark in the llvm test-suite, and >
2009 Jul 14
0
[LLVMdev] Profiling in LLVM Patch Followup 1
Hi Andreas, Thanks for breaking things up. I applied two pieces of this patch in separate no-functionality-change commits, here: http://llvm.org/viewvc/llvm-project?view=rev&revision=75623 and here: http://llvm.org/viewvc/llvm-project?view=rev&revision=75625 I merged in my changes to your patch, which results in the attached patch. There may be some missed merge errors. The main
2013 Dec 19
2
[LLVMdev] How to XFAIL test cases with buildbot LNTFactory
Hi, I am currently trying to set up new performance and regression testers for Polly and LLVM and would like to XFAIL two test cases. I am using the LNTBuilder instead of the NightlyTestBuilder out of the assumption that the LNTBuilder is the more modern solution. However, when trying to xfail test cases I realized the xfail=[] parameter of getLNTFactor is ignored. Previously this was not an
2011 Feb 26
0
[LLVMdev] [MC] Removing relaxation control
On Feb 25, 2011, at 11:38 AM, Rafael Avila de Espindola wrote: >>> Can someone else try to reproduce this? > > I tried gcc.c from > http://people.csail.mit.edu/smcc/projects/single-file-programs/ and the > difference is a bit more noticeable: > > -O0 -mno-relax-all > > real 0m13.182s > user 0m12.690s > sys 0m0.450s > > -O0 > > gcc.o is
2011 Feb 25
3
[LLVMdev] [MC] Removing relaxation control
>> Can someone else try to reproduce this? I tried gcc.c from http://people.csail.mit.edu/smcc/projects/single-file-programs/ and the difference is a bit more noticeable: -O0 -mno-relax-all real 0m13.182s user 0m12.690s sys 0m0.450s -O0 gcc.o is 10932968 bytes. real 0m12.969s user 0m12.520s sys 0m0.410s gcc.o is 11410552 bytes IMHO it would still be reasonable to switch to
2009 Mar 14
0
[LLVMdev] Coverage
Hi all, I ran some gcov numbers today for LLVM/clang on their respective test suites (on Darwin/i386). If you are interested, the results are here: http://t1.minormatter.com/~ddunbar/llvm-cov/ and here: http://t1.minormatter.com/~ddunbar/llvm-cov/clang.html High level summary is LLVM's test suite is at 70% line coverage (and that is only the tools that are run) and clang is at 80%. -
2010 Jul 11
1
[LLVMdev] MC: Object file specific parsing
On Jul 11, 2010, at 11:55 AM, Matt Fleming wrote: > On Sun, 11 Jul 2010 10:15:52 -0500, innate one <innate1 at gmail.com> wrote: >> Ping = repost to thread if no feedback given below criteria > > Heh, I think you misunderstood my reply ;-) > > I understand what 'ping' means, I was simply asking Daniel if he has had > chance to deal with this yet. Daniel
2014 Apr 30
1
[Bug 10579] New: --xattr internal abbrev error
https://bugzilla.samba.org/show_bug.cgi?id=10579 Summary: --xattr internal abbrev error Product: rsync Version: 3.1.0 Platform: All OS/Version: Mac OS X Status: NEW Severity: major Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: samba at haravikk.com
2001 Mar 16
2
Installation problems
When I try to install the tinc RPM I am missing [root@relay buytaert]# rpm -vih tinc-1.0pre2-1.i386.rpm error: failed dependencies: libgmp.so.2 is needed by tinc-1.0pre2-1 [root@relay buytaert]# ls /usr/lib/libgmp.so.3 /usr/lib/libgmp.so.3 [root@relay buytaert]# rpm -qf /usr/lib/libgmp.so.3 gmp-3.1.1-3 This seems to be a too recent version. So I tried compiling it and got the following
2012 Dec 04
3
[LLVMdev] Minimum Python Version
So, I just tried, and basically it's difficult to make progress due to the print statements (since they induce an immediate syntax error). Since 2.4 doesn't support `from __future__ import print_function`, the only alternative I guess is shimming in a print function. This is a maintenance effort that I don't want to do right now (and, TBQH, I feel that the proper maintainer should be
2012 Dec 04
0
[LLVMdev] Minimum Python Version
Hi Sean, If there was a concrete need to move to a newer Python version in order to make lit Python 3 compatible, I would view that as a good reason to move forward. I have little experience writing Python 2 & 3 compatible code, so I'd need to see the patch to make lit Python 3 compatible before I could comment more. - Daniel On Tue, Dec 4, 2012 at 9:15 AM, Sean Silva <silvas at