search for: 0x7fff

...'m curious why 'unsigned short w = 0x8000' is displayed as -32768 in the IR? This propagates to the DAG and hence tablegen, where I am missing matching on some immediates because the immediate is not being looked at as unsigned? For example, we have no issue if instead of 0x8000 we use 0x7FFF, then everything is fine, the match is fine. I can understand that it's just being printed as 'signed' even when it's unsigned due to the bit pattern (2s complement) but it seems to affect matching. We'd like; unsigned short x, y; int main() { unsigned short w = 0x8000;...

Right, I understand that. So why is 0x7FFF matching fine but not 0x8000 both fit in 16 bit? Thanks. On Wed, Feb 15, 2017 at 1:24 PM, Reid Kleckner <rnk at google.com> wrote: > LLVM IR integers have no sign. You can't reliably tell whether an add or > subtract was signed or unsigned when generating code. > > On Wed,...

Thanks for your reply. We are propagating sign info to tablegen currently using BinaryWithFlagsSDNode.Flags.hasNoSignedWrap atm. I imagine (I have not looked) they are printed according to instruction in AsmPrinter.cpp (pure speculation). I'm still confused as to why 0x7FFF is ok to match 16 bit int but not 0x8000? Thanks. On Wed, Feb 15, 2017 at 1:44 PM, Manuel Jacob <me at manueljacob.de> wrote: > Hi Ryan, > > It is important to get clear about that LLVM IR integers (and operations > if they don't have to) have no sign. But IR integers have...

...I imagine (I have not looked) they are printed according to >>> instruction in >>>> AsmPrinter.cpp (pure speculation). >>>> >>> >>> I'm not quite sure what you're referring to. >>> >>> I'm still confused as to why 0x7FFF is ok to match 16 bit int but not >>>> 0x8000? >>>> >>> >>> I can't answer this question without knowing how your patterns look >>> like >>> exactly, but possibly this happens specifically because you try to >>> propagate s...

...;signedness" when using two's > complement. > > I imagine (I have not looked) they are printed according to instruction in >> AsmPrinter.cpp (pure speculation). >> > > I'm not quite sure what you're referring to. > > I'm still confused as to why 0x7FFF is ok to match 16 bit int but not >> 0x8000? >> > > I can't answer this question without knowing how your patterns look like > exactly, but possibly this happens specifically because you try to > propagate sign info (which doesn't really work, as explained above). &g...

...PUS lib under PIC32MZ, using the MIPS configuration. It compiles correctly and it seems that all the procedures invoked returns no error. However, when I excite the encoder with a pure 1 kHz tone, the encoding/decoding procedure returns al the samples to silence (the buffer is filled with 0x8001 or 0x7fff). The configuration is 48000 sps, 64kHz bandwidth, two channels, OPUS_APPLICATION_AUDIO application. The lib version is 1.1.3. The initialization procedure is as follows: _encoder = opus_encoder_create(48000, 2, OPUS_APPLICATION_AUDIO, &error); error = opus_...

...I master a recording of a long performance. I still support enhancements to the flac command line to support direct conversion to one or more formats that do not have a 2 GB limit, but for most audio formats libsndfile might be acceptable. Hopefully, libsndfile no longer uses the incorrect 0x7FFF (32767) factor for float to 16-bit integer conversions, because that would make it unacceptable for lossless file conversions. Brian Willoughby Sound Consulting

Hi, So SCEV cannot simplify that expression to -1 because of overflow issues (take e.g. src=0x7FFF..). If you compile with 64 bits integers, then the sexts disappear and so SCEV can do the simplification. Depending on what you want to do, you may want to either do not extend src and dst to 64 bits or add a NSW flag to the computations. That will hopefully make SCEV push the sext outside and t...

I have a pair of SCEVs that appear different to me. However, when I compute the difference, it's not known to be non-zero. src = (sext i32 %n to i64) dst = (sext i32 (1 + %n) to i64) delta = ((sext i32 %n to i64) + (-1 * (sext i32 (1 + %n) to i64))) Is this behavior expected? If I repeat the experiment with 64-bit ints (or unsigned), things work out like I expect. 32-bit

...in_range = 50; else if (st->nb_adapt < 10000) min_range = 150; else min_range = 300; ... </> Maybe something like this is required within speex_preprocess_run to prevent the observed overflow. <preprocess.c speex_preprocess_run> ... if ( st->nb_adapt < 0x7FFF /* or 32767 as elsewhere in the code */ ) st->nb_adapt++; ... </> Thanks. Peter Rowling

On Mar 6, 2011, at 01:22, Erik de Castro Lopo wrote: > Brian Willoughby wrote: >> Hopefully, libsndfile no longer uses the incorrect 0x7FFF (32767) >> factor for float to 16-bit integer conversions, because that would >> make it unacceptable for lossless file conversions. > > That is a statement of opinion rather than fact but I won't go into > that here. It is a statement of mathematical fact, not opinion....

...d_buf = 1; - ds->depth = depth; -#ifdef CONFIG_OPENGL - if (opengl_enabled) { - ds->dpy_update = opengl_update; - } -#endif + dcl->dpy_setdata(ds); } /* generic keyboard conversion */ @@ -525,8 +424,8 @@ } SDL_GetMouseState(&dx, &dy); - dx = dx * 0x7FFF / (screen->w - 1); - dy = dy * 0x7FFF / (screen->h - 1); + dx = dx * 0x7FFF / (real_screen->w - 1); + dy = dy * 0x7FFF / (real_screen->h - 1); } else if (absolute_enabled) { sdl_show_cursor(); absolute_enabled = 0; @@ -538,7 +437,7 @@ static void toggle_fu...

ingress can be used to control the incoming packet, such as: tc qdisc add dev eth0 handle ffff: ingress tc filter add dev eth0 parent ffff: protocol ip prio 5 u32 match ip src 172.16.1.11 police rate 10kbit burst 10k drop flowid :1 tc filter add dev eth0 parent ffff: protocol ip prio 5 u32 match ip src 172.16.1.22 police rate 10kbit burst 10k drop flowid :2 first ,I do not sure these method can

> OK, attempting one more convergence on all this, here's > what I did: > > 1. Reverted back to rev 1.5 of src/libFLAC/ia32/Makefile.am > 2. Applied Matt's last cleanup patch of 8 files. I did not > apply the patch to src/test_unit/main.c since it looks wrong. > main.c is supposed to include the local bitbuffer.h, not > src/libFLAC/private/bitbuffer.h; I think the

...> @@ -237,15 +237,6 @@ struct tgsi_declaration_array { > unsigned Padding : 22; > }; > > -/* > - * Special resources that don't need to be declared. They map to the > - * GLOBAL/LOCAL/PRIVATE/INPUT compute memory spaces. > - */ > -#define TGSI_RESOURCE_GLOBAL 0x7fff > -#define TGSI_RESOURCE_LOCAL 0x7ffe > -#define TGSI_RESOURCE_PRIVATE 0x7ffd > -#define TGSI_RESOURCE_INPUT 0x7ffc > - This should be in a separate patch with "gallium:" as prefix even if nouveau is the only driver which somehow uses these constants. Other than that, the p...

...b/src/gallium/include/pipe/p_shader_tokens.h @@ -237,15 +237,6 @@ struct tgsi_declaration_array { unsigned Padding : 22; }; -/* - * Special resources that don't need to be declared. They map to the - * GLOBAL/LOCAL/PRIVATE/INPUT compute memory spaces. - */ -#define TGSI_RESOURCE_GLOBAL 0x7fff -#define TGSI_RESOURCE_LOCAL 0x7ffe -#define TGSI_RESOURCE_PRIVATE 0x7ffd -#define TGSI_RESOURCE_INPUT 0x7ffc - #define TGSI_IMM_FLOAT32 0 #define TGSI_IMM_UINT32 1 #define TGSI_IMM_INT32 2 -- 2.7.2

...xxx.yyy.zzz.XXX .... OOPS, forgot to remove a old ListenAddress for a removed interface... Did that and HUP-ed sshd # lsof ... sshd 11152 root 6u IPv4 0x7004ded8 0t0 TCP xxx.yyy.zzz.hhh:22 (LISTEN) ... That is, a Listen config line for a non-existing address gives a shadow port on ((-1 & 0x7fff) - 22). Rather spooky... cheers, Torbj?rn Wictorin, Uppsala univ.

Hello! My users get warnings about their passwordss expiring. I dont want them to need to change password. I set the Accountpoliicy for max. passwd age to 0 but that doesn't affect the expiration date. What is the correct way to do it? Thanks in advance! Yours, Rudolf -- A mathematician is a machine, that converts coffee into theorems. Rudolf Weeber Muehlrain 9 70180 Stuttgart Tel: 0711

Commit c3083c7082 ("nv50/ir: add support for BUFFER accesses") disabled / commented out some of the old resource handling code, but not all of it. Effectively all of it is dead already, if we ever enter the old code paths in handeLOAD / handleSTORE / handleATOM we will get an exception due to trying to access the now always zero-sized resources vector. Disable all the dead code.

This may be answered somewhere but i tried googling for it with no luck, so... What''s the limit on number of traffic classes (classid) you can define on Linux ? -- Using M2, Opera''s revolutionary e-mail client: http://www.opera.com/m2/ _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc