Displaying 20 results from an estimated 38 matches for "breg".
Did you mean:
berg
2006 May 06
2
can''t find a register in class `BREG'' while reloading `asm''
...I/var/tmp/portage/xen-3.0.2/work/xen-3.0.2/xen/include/asm-x86/mach-default
-msoft-float -g -D__XEN__ -c multicall.c -o multicall.o
memory.c: In function `guest_remove_page'':
/var/tmp/portage/xen-3.0.2/work/xen-3.0.2/xen/include/asm/mm.h:206:
error: can''t find a register in class `BREG'' while reloading `asm''
make[2]: *** [memory.o] Error 1
make[2]: *** Waiting for unfinished jobs....
multicall.c: In function `do_multicall'':
multicall.c:43: error: can''t find a register in class `BREG'' while
reloading `asm''
make[2]: *** [multica...
2007 Feb 11
1
syslinux-3.36 nopie patch
I made a patch that depending of gcc flavor add -no-pie or -nopie on
libutil and dos Makefile.
This fix fatal error like this
sha1hash.c: In function `SHA1Transform':
../include/netinet/in.h:24: error: can't find a register in class `BREG'
while reloading `asm'
../include/netinet/in.h:24: error: can't find a register in class `BREG'
while reloading `asm'
../include/netinet/in.h:24: error: can't find a register in class `BREG'
while reloading `asm'
...
Gilles
-------------- next part --------------
A...
2011 Dec 09
1
[PATCH] Fix compilation when gcc is patched to default to -fPIE -Wl, -pie
gcc hardened by default is seen on gentoo, alt-linux, HLFS, etc.
Patch fix on syslinux this error during gpxe compilation:
[BUILD] bin/cpu.o
arch/i386/core/cpu.c: In function 'get_cpuinfo':
arch/i386/include/bits/cpu.h:79: error: can't find a register in class 'BREG' while reloading 'asm'
arch/i386/include/bits/cpu.h:79: error: can't find a register in class 'BREG' while reloading 'asm'
arch/i386/include/bits/cpu.h:79: error: can't find a register in class 'BREG' while reloading 'asm'
arch/i386/include/bits/c...
2013 Oct 04
1
[LLVMdev] ADDE to use branch registers
...nstruction pattern. The following code snippet is not really working for me:
SDValue rvexTargetLowering::
LowerAddCG(SDValue Op, SelectionDAG &DAG) const
{
unsigned Opc = Op.getOpcode();
SDNode* N = Op.getNode();
EVT VT = Op.getValueType();
DebugLoc dl = N->getDebugLoc();
SDValue BReg = DAG.getTargetConstant(rvex::B0, VT); // Add extra register to output
return DAG.getNode(rvexISD::Addc, dl, VT, N->getOperand(0), N->getOperand(1), BReg);
}
Could anybody advice me on a way to make the backend know that the ADDE instruction will cause a branch register to be used?
Tha...
2011 Dec 06
4
Last call for 4.05
I'm going to try to push 4.05 out this week, so please holler if there
is anything critical missing.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
2004 Apr 05
3
Selecting Best Regression Equation
...),
2. 'Backward Elimination Procedure' ,
3. 'Forward Selection Procedure' ,
4. 'Stepwise Regression Procedure' (as SAS's PROC REG /METHOD = STEPWISE /
FORWARD / BACKWARD which methods are also available in SPSS) or
5. 'Best subset selection (as MINITAB's BREG - BEST k command)'.
Any response / help / comment / suggestion / idea / web-link / replies will
be greatly appreciated.
Thanks in advance for your time.
_______________________
Mohammad Ehsanul Karim <wildscop at yahoo.com>
Institute of Statistical Research and Training
University o...
2016 Feb 01
2
TableGen customized node with mayStore attribute is deleted if there is no use
...implementation is wrong.
def MoveTy : SDTypeProfile<1, 1, []>;
def MoveFlag : SDNode<"FOOISD::MOVE_FLAG", MoveTy, [SDNPHasChain,
SDNPSideEffect, SDNPMayStore, SDNPMayLoad]>;
let hasSideEffects = 1, mayStore = 1, mayLoad = 1 in {
def MOVE : InstFOO<(outs ARegs:$dst), (ins BRegs:$src),
"move $dst, $src",
[(set i32:$dst, (MoveFlag i32:$src))]>;
For example, I add this node into SDAG when I want to move the formal
argument from the specific register class to other register class. I
implement it in LowerFormalArguments()...
2010 Jul 18
2
Problem With Steam
...supported
fixme:threadpool:RtlQueueWorkItem Flags 0x4 not supported
fixme:threadpool:RtlQueueWorkItem Flags 0x4 not supported
fixme:threadpool:RtlQueueWorkItem Flags 0x4 not supported
fixme:threadpool:RtlQueueWorkItem Flags 0x4 not supported
fixme:dbghelp_dwarf:compute_location Only supporting one breg (18 -> 24)
fixme:dbghelp_dwarf:compute_location Only supporting one breg (17 -> 23)
fixme:dbghelp_dwarf:compute_location Only supporting one breg (17 -> 23)
I use Wine 1.2 and i use a network Wifi.
Thanks for your help.
2008 Dec 12
5
[PATCH 0/5] ia64/pv_ops, xen: binary patch optimization TAKE 2
This patch set is intended for the next merge window. They are just
enhancements of the already merged patches or ia64 porting from x86
paravirt techniques and that their quality is enough for merge.
This patch set is for binary patch optimization for paravirt_ops.
The binary patch optimization is important on native case because
the paravirt_ops overhead can be reduced by converting indirect
2008 Dec 12
5
[PATCH 0/5] ia64/pv_ops, xen: binary patch optimization TAKE 2
This patch set is intended for the next merge window. They are just
enhancements of the already merged patches or ia64 porting from x86
paravirt techniques and that their quality is enough for merge.
This patch set is for binary patch optimization for paravirt_ops.
The binary patch optimization is important on native case because
the paravirt_ops overhead can be reduced by converting indirect
2008 Dec 22
5
[PATCH 0/5] ia64/pv_ops, xen: binary patch optimization TAKE 3
This patch set is intended for the next merge window. They are just
enhancements of the already merged patches or ia64 porting from x86
paravirt techniques and that their quality is enough for merge.
This patch set is for binary patch optimization for paravirt_ops which
depends on the patch series I sent out, ia64/pv_ops, xen:
more paravirtualization.
The binary patch optimization is important on
2008 Dec 22
5
[PATCH 0/5] ia64/pv_ops, xen: binary patch optimization TAKE 3
This patch set is intended for the next merge window. They are just
enhancements of the already merged patches or ia64 porting from x86
paravirt techniques and that their quality is enough for merge.
This patch set is for binary patch optimization for paravirt_ops which
depends on the patch series I sent out, ia64/pv_ops, xen:
more paravirtualization.
The binary patch optimization is important on
2009 Mar 04
5
[PATCH 0/5] ia64/pv_ops, xen: binary patch optimization TAKE 4
This patch set is for the next merge window.
They are just enhancements of the already merged patches or ia64 porting
from x86 paravirt techniques and that their quality is enough for merge.
This patch set is for binary patch optimization for paravirt_ops which
depends on the patch series I sent out, ia64/pv_ops, xen:
more paravirtualization.
The binary patch optimization is important on native
2009 Mar 04
5
[PATCH 0/5] ia64/pv_ops, xen: binary patch optimization TAKE 4
This patch set is for the next merge window.
They are just enhancements of the already merged patches or ia64 porting
from x86 paravirt techniques and that their quality is enough for merge.
This patch set is for binary patch optimization for paravirt_ops which
depends on the patch series I sent out, ia64/pv_ops, xen:
more paravirtualization.
The binary patch optimization is important on native
2008 Nov 25
6
[PATCH 0/5] ia64/pv_ops, xen: binary patch optimization
This patch set is for binary patch optimization for paravirt_ops.
The binary patch optimization is important on native case because
the paravirt_ops overhead can be reduced by converting indirect
call into in-place execution or direct call.
The first patch imports helper functions which themselves doesn't interesting
things.
The second patch replaces the indirect function calls with a
2008 Nov 25
6
[PATCH 0/5] ia64/pv_ops, xen: binary patch optimization
This patch set is for binary patch optimization for paravirt_ops.
The binary patch optimization is important on native case because
the paravirt_ops overhead can be reduced by converting indirect
call into in-place execution or direct call.
The first patch imports helper functions which themselves doesn't interesting
things.
The second patch replaces the indirect function calls with a
2014 Sep 02
2
[LLVMdev] Instruction Selection sanity check
Hi,
I am working on a new back-end for LLVM. This architecture has two register
types, data(A) and accumulator(B).
A registers are i32 where as B registers are i64. This is causing me some
headaches, as far as I can tell, it's not really possible to mix the two
using tablegen?
In the hardware, every instruction can either take an A register or a B
register, in tablegen (as far as I can
2011 Sep 14
2
Hard Reset Demo doesn't render textures
...ing UseGLSL to disabled didn't changed anything. I have installed d3dx9_36 and vcrun2008 with winetricks.
This is output from the terminal (wine.log):
Code:
fixme:dbghelp_dwarf:compute_location Only supporting one reg (edx/19 -> -2)
fixme:dbghelp_dwarf:compute_location Only supporting one breg (ecx/18 -> edx/19)
fixme:xinput:XInputGetState (0 0xc0b848)
fixme:win:EnumDisplayDevicesW ((null),0,0x32f234,0x00000000), stub!
fixme:ddraw:DirectDrawEnumerateExA flags 0x00000001 not handled
fixme:wbemprox:wbem_locator_ConnectServer 0x4f7ae20, L"\\\\.\\root\\cimv2", (null), (null), (n...
2010 Sep 05
1
Memory.dll.??0MemoryPoolObj@@QAE@PBDW4MEMPOOLTYPE@@I@Z
...pi:SetEntriesInAclA 1 0x33f7c4 (nil) 0x33f80c
fixme:advapi:SetSecurityInfo stub
fixme:dpnhpast:DllRegisterServer :stub
wine: Call from 0x7ef93900 to unimplemented function Memory.dll.??0MemoryPoolObj@@QAE at PBDW4MEMPOOLTYPE@@I at Z, aborting
fixme:dbghelp_dwarf:compute_location Only supporting one breg (18 -> 24)
Could not load wine-gecko. HTML rendering will be disabled.
I have never seen that dll before. There isn't one in my Windows 7 installation. What should I do with this??
Thanks!
2017 Sep 06
4
RFC: Introduce DW_OP_LLVM_memory to describe variables in memory with dbg.value
...DIExpressions. If the value is ultimately register
allocated and the DIExpression is empty, we will emit a DW_OP_regN location
expression. If the value is spilled, we usually don't need to append
DW_OP_stack_value because the location is now a memory location, which can
be described by DW_OP_[f]breg.
Today, passes that want to add "plus 3" to a DIExpression go out of their
way to add DW_OP_stack_value to the DIExpression because the backend won't
do it for us, even though dbg.value normally describes the value, not an
address.
To explore the alternative DW_OP_stack_value model,...