Displaying 3 results from an estimated 3 matches for "ui4".
Did you mean:
u64
2011 Jan 19
2
[LLVMdev] How to avoid register reuse in machine instructions?
Is there a way to force the register allocator to avoid reusing an
operand register for a definition? For example, the following machine
instruction reuses a register for the first operand and definition:
%uI7<def> = eq at III %uI7<kill>, %uI4
I'd like:
%uI8<def> = eq at III %uI7<kill>, %uI4
I'm guessing that the right way to do this would be to kill the operand
registers after the given machine instruction rather than before it, but
I don't see a way to mark it this way.
Andrew
2024 Jul 15
1
Request for a Lockdown option
...1884, 2133)?
if(
#if(SF_64BIT)
m_ip6.a64[0] == 0
#else
m_ip6.a32[0] == 0
&& m_ip6.a32[1] == 0
#endif
&& m_ip6.a16[4] == 0 // a32[2] == 0 || a32[2] == NTOH(0x0000FFFF)
) {
ui4 i = m_ip6.a32[3];
m_ip4 = i;
switch(m_ip6.a16[5]) {
case 0xFFFF: // mapped
m_flags = f_map4;
goto jchk;
case 0x0: // compatible?
m_flags...
2024 Jul 15
1
Request for a Lockdown option
Hi,
On Sun, Jul 14, 2024 at 10:25:46AM +0100, Brian Candler wrote:
> On 14/07/2024 03:49, Steffen Nurpmeso wrote:
> > I have read
> >
> > https://datatracker.ietf.org/doc/html/draft-cmetz-v6ops-v4mapped-api-harmful-01
> >
> > but as an application developer i find it ugly not to be able to
> > "simply do it", and get back a mapped address.