Displaying 5 results from an estimated 5 matches for "predefinitions".
Did you mean:
redefinitions
2003 Jan 24
0
problem with iproute and TEQL over predefinited tables
hi, I''ve encrountred some problem with iproute2...
I''m building a router with kernel 2.4.20 but my script fail when I try to do
a load balancing over a specific traffic, how explained on LARTC for
balance the access between more link we should simple:
ip route add default scope global nexthop via IP1 dev ETH0 weight 1 \
nexthop via IP2 dev ETH1 weight 1
for specific traffic
2001 Mar 02
3
Winelib problems
I'd like to know how to link console functions such as
WriteConsoleOutputA.
They are documented as implemented, and I can compile source code
including these function predefinitions, but I get undefined errors when
linking. I don't know which library to add to get objects linked.
Thanks in advance. Ignasi Villagrasa.
2012 Jul 17
0
[LLVMdev] [cfe-dev] Curent svn build, generates llvm DEBUG builds
...ium-Pro and above
> x86-64 - 64-bit X86: EM64T and AMD64
> xcore - XCore
>
> Why I get DEBUG builds?
It has been since r29020. :D
depends on definition of __OPTIMIZE__ .
Your llc.exe should be built with Release, if llc is bin/Release/llc.exe .
I won't find corresponding predefinitions in cl.exe.
http://msdn.microsoft.com/en-us/library/b0084kay(v=vs.100).aspx
Shall we suppress the line "DEBUG build." under cl.exe ?
...Takumi
2008 May 14
0
[LLVMdev] malloc, magic, and embedded compilation
> 1. The particular optimization that was done there was based on the
> compiler substituting an alternate implementation of malloc(). This may
> not be appropriate in kernel or deeply embedded systems. Is there a way
> for someone who is building that sort of system to enable/disable the
> builtin library magic selectively?
-ffreestanding
> I assume that LLVM can support
2008 May 14
4
[LLVMdev] malloc, magic, and embedded compilation
The discussion of malloc optimization from two (three?) weeks ago
prompts me to be concerned about implications for kernel compilation.
Basically, I have two questions:
1. The particular optimization that was done there was based on the
compiler substituting an alternate implementation of malloc(). This may
not be appropriate in kernel or deeply embedded systems. Is there a way
for someone who is