search for: contantly

Displaying 20 results from an estimated 82 matches for "contantly".

Did you mean: constantly
2013 Jun 26
2
[LLVMdev] Contants generation - proposal
> I think that the improved behavior for consts should be acceptable in the large model. But that's just me. By default, all constants should be in a special read-only section, and this section may be far from the text section. I'm working with JIT model or with only one object file. The code model, when all constants are near, we can call "LargeJIT". (Is it sounds better
2013 Jun 25
2
[LLVMdev] Contants generation
Hi again, Actually, I've just been looking at the existing code and the ARM solution may be over-complicated for this situation. You should be able to override EmitConstantPool directly, or possibly even just override getSectionForConstantKind in X86LinuxTargetObjectFile (and perhaps others) to return .text. Tim.
2013 Jun 25
0
[LLVMdev] Contants generation
That what I actually did now, locally in the code. But I still see the " movabsq" .text .align 8, 0x90 .LCPI0_0: .quad 4606281698874543309 # double 0.9 .LCPI0_1: .quad 4631147119616759172 # double 42.2794408 .LCPI0_2: .long 1065353216 # float 1 .zero 4 ... movabsq $.LCPI0_1, %rax # encoding: [0x48,0xb8,A,A,A,A,A,A,A,A]
2013 Jun 26
0
[LLVMdev] Contants generation - proposal
>> I think that the improved behavior for consts should be acceptable in the large model. But that's just me. > By default, all constants should be in a special read-only section, and this section may be far from the text section. Why should they? The only reason I can think of is to support execute-only pages, but isn't that the less common use-case? From what I could tell from
2013 Jun 25
0
[LLVMdev] Contants generation - proposal
Hi Elena, > (2) Proposal > Define one more Code Model, let's say "LargeNearConst", which will allow to put constants in .text. Isn't that a little heavy-handed? The large model only requires the less efficient access for symbols we can't control, and in fact x86 still uses pc-relative conditional branches within a function so it can't pretend to support a single
2013 Jun 25
2
[LLVMdev] Contants generation - proposal
Hi all, I analyzed more and ready (1) to describe the problem and (2) I have a proposal. (1) Problem description: In X86_64 target the Code Model is "Large". It means that address is 64-bit and IP-relative memory operand can't be used in this case. (Because in IP-relative memory operand the displacement is 32-bit). In order to load constant, we use 2 instructions. movabsq
2013 Jun 24
2
[LLVMdev] Contants generation
Hi, I'd like to generate constants inside .text in order to use ip-relative loads, when the code model is "large". How can I do this? (I'm on X86_64 linux) Thank you. - Elena --------------------------------------------------------------------- Intel Israel (74) Limited This e-mail and any attachments may contain confidential material for the sole use of the
2013 Jun 25
0
[LLVMdev] Contants generation
Hi Elena, > I’d like to generate constants inside .text in order to use ip-relative > loads, when the code model is “large”. I don't think this is a sequence the x86 backend supports at the moment, but it is how ARM handles its constant-pools. The outline is that you have a pass which looks through a functions constpool uses and emits a pseudo-instruction for each, which is then
2007 Aug 20
0
[LLVMdev] Problem with missing support for non-zero contant initializers.
On 8/20/07, Anton Korobeynikov <asl at math.spbu.ru> wrote: > Hello, Tomas. > > > So far I have only been using LLVM at the user level. And I'm not sure > > how this problem should be solved. It would be really nice if there > > was a way to specify something like: > > ******************************************************************* > >
2007 Aug 20
0
[LLVMdev] Problem with missing support for non-zero contant initializers.
On Mon, 20 Aug 2007, Tomas Lindquist Olsen wrote: > I'm working on a LLVM based compiler for the D programming language by > Walter Bright. Nifty. > D allows static arrays up to 16MB in size. I'm initializing global > static arrays with a constant initializer. But D requires that (per > default) static arrays are initialized with the default initializer > for the
2007 Aug 20
1
[LLVMdev] Problem with missing support for non-zero contant initializers.
> > D allows static arrays up to 16MB in size. I'm initializing global > > static arrays with a constant initializer. But D requires that (per > > default) static arrays are initialized with the default initializer > > for the element type. For float this happens to be NaN, so I cannot > > use a 'zeroinitializer'. > > Wow, this *is* bad. I think
2007 Aug 20
1
[LLVMdev] Problem with missing support for non-zero contant initializers.
Chris Lattner wrote: >> D allows static arrays up to 16MB in size. I'm initializing global >> static arrays with a constant initializer. But D requires that (per >> default) static arrays are initialized with the default initializer >> for the element type. For float this happens to be NaN, so I cannot >> use a 'zeroinitializer'. > > Wow, this *is*
2008 Dec 13
1
need to initialize contant arrays , where to do it...
I need to load names, from the table ''domains'' into an array (frequently used in my app..) ALL_DOMAINS = Domain.find(:all).map { |d| d.name }.compact I tried to write it in an initialize or in my application.rb BUT problem : when I run a rake db:migrate initially (after creating the database) I get an error.. rake db:migrate --trace (in
2007 Aug 20
2
[LLVMdev] Problem with missing support for non-zero contant initializers.
Hello, Tomas. > So far I have only been using LLVM at the user level. And I'm not sure > how this problem should be solved. It would be really nice if there > was a way to specify something like: > ******************************************************************* > @_D9arrayinit5tableG32f = global [32 x float] [ 32 x float 0x7FF8000000000000 ] >
2007 Aug 20
5
[LLVMdev] Problem with missing support for non-zero contant initializers.
Hi all. I'm working on a LLVM based compiler for the D programming language by Walter Bright. D allows static arrays up to 16MB in size. I'm initializing global static arrays with a constant initializer. But D requires that (per default) static arrays are initialized with the default initializer for the element type. For float this happens to be NaN, so I cannot use a
2007 Oct 19
2
logrotation
Dear all Salam, i have installed logrotation package in BSD, the script runs every night at 3:00 pm night and makes filename.1.gz. but when i use less command to see this gz file it says "do u want to see binary file??" through which utility i can see the contants of the file??? Regards, Umair Shakil ETD -------------- next part -------------- An HTML attachment was scrubbed... URL:
2010 Nov 05
5
Ongoing performance issues with 2.0.x
Due to the ongoing performance issues with 2.0.x I switched back to 1.2.15 yesterday evening, with no changes to the machine or my users. (I migrated from 1.2.15 to 2.0.x by converting the existing config) Today, we have MUCH LESS load, with the same number of logins/min. I cannot say what exactly causes this immense increase in load, but one observation is that the time spent in system() has
2019 Jun 03
2
How to fix mapping Administrator to root
Hi Rowland, I have checked that Adinistrator is a member of "Domain Admins" in ADUC. Base Permission of the share folder is 0770 and own is root and the groups is "domain admins" in linux. since "smbstatus -b" show that administrator's group is root. Is this related to my previous configuration? I once give a uidNumber to administrator. here's full contant
2006 May 23
4
[LLVMdev] Spilling register and frame indices
Hi, right now, LLVM does register spilling by: 1. Creating stack object 2. Passing index of that stack object to MRegisterInfo::storeRegToStackSlot 3. At later stage, frame indices are replaced by calling to MRegisterInfo::eliminateFrameIndex. This works for me, but there's slight problem. The target does not have "register + contant" addressing mode, so accessing frame index
2024 Jan 12
1
chmod of smbpasswd file
...r than > owner. https://bugzilla.samba.org/show_bug.cgi?id=15555 Filed a bug and a patch is proposed: add fstat() to bypass [f]chmod() if the password file has valid permissions 0600. We had a similar case before, a bit different is the password file is resident on a writable ext3/ext4, and contantly [f]chmod() might have a performance impact on entry-level systems since dirty pages syncing is expensive, hope this helps :) -- Regards, Jones Syue | ??? QNAP Systems, Inc.