Displaying 20 results from an estimated 30000 matches similar to: "[LLVMdev] RFC: better method names"
2005 Feb 27
2
[LLVMdev] Measuring performance overhead
On Sat, 2005-02-26 at 22:34 -0600, Chris Lattner wrote:
> On Sat, 26 Feb 2005, Tanu Sharma wrote:
>
> > Thanks for the reply :-)
> > I am actually looking for ways to determine "size" of code segment when the program is in native code.
> > Any suggestions to do that ?
>
> Compile it with llvm to a native .o or .exe file, then run 'size' on it?
>
2007 Nov 02
3
[LLVMdev] [Fwd: Fwd: LLVM and threading]
Dear All,
Here's a question Vikram and I received. Is the LLVM JIT thread safe?
-- John T.
-------------- next part --------------
An embedded message was scrubbed...
From: "Adve, Vikram Sadanand" <vadve at uiuc.edu>
Subject: Fwd: LLVM and threading
Date: Thu, 1 Nov 2007 09:48:59 -0500
Size: 3037
URL:
2005 Feb 27
0
[LLVMdev] Problem in compilation (native option)
Thanks for replying .
I came across another problem while trying it.
The following compilation is not working: ( with the native option)
llvmgcc x.c -o a.out -Wl,-native
I get this error:
gccld: a.out.s: Can't destroy file: ut.s
How can I fix that ?
Thanks
Tanu
Andrew Lenharth <alenhar2 at cs.uiuc.edu> wrote:
On Sat, 2005-02-26 at 22:34 -0600, Chris Lattner wrote:
> On
2005 May 14
0
[LLVMdev] debian
On Sat, May 14, 2005 at 02:18:26AM +0200, Stefan Strasser wrote:
> in case you're interested in having llvm in debian sarge: it was
> removed today. I don't know why, but you might want to find out
> because sarge is in freeze phase for release next month.
Possibly because of these:
http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=llvm
I addressed the first one and fixed it in
2005 May 14
3
[LLVMdev] debian
in case you're interested in having llvm in debian sarge: it was removed
today. I don't know why, but you might want to find out because sarge is
in freeze phase for release next month.
regards,
--
Stefan Strasser
2008 Nov 24
1
[LLVMdev] how to track down a kernel miscompilation?
One other note I forgot...
sig_sysreturn (arch/x86/kernel/signal_32.c) has a magic fudge factor
to fix up stack layout differences between llvm and gcc. If when you
hit userspace you get signal handling errors, look at the frame
addresses printed out and adjust the fudge factor to make the frame
addresses match. (the code automatically enables the debug output
after the first signal frame
2006 Jun 07
2
script/generate scaffold pluralizes class names
Hi everyone,
I''m a rails & ruby nuby, and this is my first post to the list.
Here''s my environment in case it helps diagnose my problem:
Ruby version
1.8.4 (powerpc-darwin8.6.0)
RubyGems version
0.8.11
Rails version
1.1.2
Active Record version
1.14.2
Action Pack version
1.12.1
Action Web Service version
1.1.2
Action Mailer version
1.2.1
Active Support version
1.3.1
I did
2005 Feb 28
1
[LLVMdev] Problem in compilation (native option)
On Sun, 27 Feb 2005, Tanu Sharma wrote:
> Thanks for replying .
> I came across another problem while trying it.
> The following compilation is not working: ( with the native option)
>
> llvmgcc x.c -o a.out -Wl,-native
>
> I get this error:
>
> gccld: a.out.s: Can't destroy file: ut.s
>
> How can I fix that ?
This bug has been fixed in CVS, please update your
2005 May 14
2
[LLVMdev] debian
On Fri, 2005-05-13 at 19:51 -0500, Misha Brukman wrote:
> The second one is a "serious policy violation", which isn't as clear to
> me what the bug reporter is saying, but it mentions warnings during
> doxygen build and missing fonts and related issues that I'm not quite
> following.
(CCing the bug and thus the submitter)
sounds like a missing built-depends, at
2017 Aug 03
2
explorer.exe: no mapping between names and security ids was done
... I just want to put this somewhere easily searchable based on the users error message.
Upgrading a domain controller to Debian 8 (samba 3 to 4) resulted in the message "no mapping between names and security
ids was done" at times. The message appears on the windows 7 domain pcs when running explorer.exe. Also other basic
things did not work: internet explorer, or mapping between
2005 Jun 17
1
[LLVMdev] varargs heads up
Sometime this weekend (or today) vararg support will change. vanext
will go away, and the intrinsic signatures will change. Backwards
compatibility code will be included so front ends won't need to change
initially (after that code is tested, then we will upgrade llvm-gcc).
What should work after the transition:
All Pattern based ISels (default on x86, PPC, Alpha, IA64)
Existing .bc and .ll
2008 Nov 24
0
[LLVMdev] how to track down a kernel miscompilation?
For people who want to try hacking on the linux kernel with llvm, here
is a head start:
http://llvm.org/~alenhar2/k.tbz
This is a 2.6.27.5 kernel with a .config file for qemu/kvm with virtio
devices (I also think it will work with the default devices). The
build process uses llvm-gcc -> opt -> llc so you can add your own
(per-file) passes to the build process or debug specific passes.
2016 Aug 25
1
sort.int(c(2, NA, 4), index.return=TRUE, na.last=NA, method)$ix differ for method="radix" and "shell"/"quick" (+ new default in R-devel)
Does sort.int(c(2,NA,4), index.return=TRUE, na.last=NA,
method="radix")$ix give the intended result, because I get:
> sort.int(c(2,NA,4), index.return=TRUE, na.last=NA, method="radix")
$x
[1] 2 4
$ix
[1] 1 3
With method="shell" and method="quick" in R devel, I get:
> sort.int(c(2,NA,4), index.return=TRUE, na.last=NA, method="shell")
$x
2017 Aug 10
1
Blank printers names while browsing remote printers from windows
Hi friends.
This morning waking up is painfull.
We've got a
great CUPS+Samba+Winbind print server sharing 30+ printers to our
windows clients.
Until this morning no issue, used on production for a
couple of weeks.
Today, the printer shares became unbrowsable from
windows. We can see the printers names from samba share :
"\printserver", but when we click on the "Show
2003 Feb 12
1
((AllowUsers || AllowGroups) && !(AllowUsers && AllowGroups))
Hey everyone,
After discussing the AllowGroups I think I've discovered a bug.
The system is a solaris 8 system and the problem is that when I use
AllowGroups with no AllowUsers args, the proper actions happen. Same
with AllowUsers and no AllowGroups. When I try to combine the two, none
of the Allow directives seem to take.
Is it just me or maybe a bug?
-James
2005 Dec 02
1
[LLVMdev] RFC: Plugable intrinsics
I can think of many people that use LLVM and maintain out of tree
extentions that will likely never be incorporated into mainline.
Maintaining out of tree intrnisics takes a fair amount of work and leads
to the choice of using a single version of LLVM for a project (and thus
have to manually incorporate bug fixes) or risk untimely breakage. I
propose that the plugin be extended to allow plugable
2011 Dec 22
4
[LLVMdev] The name of LLVM
> "LLVM" is officially no longer an acronym. The acronym it once expanded too was confusing, and inappropriate almost from day 1. :) As LLVM has grown to encompass other subprojects, it became even less useful and meaningless.
>
> In short, it is just "The LLVM Project", and LLVM doesn't stand for anything anymore. It is a nice short domain name though :)
2011 Feb 09
2
file serving error
hello again list!!
I am attempting to work out how to serve files with puppet.
Here is my fileserver.conf file
# This file consists of arbitrarily named sections/modules
# defining where files are served from and to whom
# Define a section ''files''
# Adapt the allow/deny settings to your needs. Order
# for allow/deny does not matter, allow always takes precedence
# over
2005 Jun 01
3
[LLVMdev] 64-bit Linux Support
Hi!
What's the plan for support on Linux 64-bit machines? Is that actively
being worked on right now or is there a roadmap for doing this?
Thanks!
-bw
2011 Dec 22
0
[LLVMdev] The name of LLVM
On Dec 21, 2011, at 7:05 PM, 陳韋任 wrote:
>> "LLVM" is officially no longer an acronym. The acronym it once expanded too was confusing, and inappropriate almost from day 1. :) As LLVM has grown to encompass other subprojects, it became even less useful and meaningless.
>>
>> In short, it is just "The LLVM Project", and LLVM doesn't stand for anything