search for: c64

...fles and other low-level data manipulation. Users that wish to examine IR directly will see much less gobbbledygook and can more easily reason about the IR. Types This proposal introduces new Single Value types to represent complex numbers. c32 - like float complex or std::complex<float> c64 - like double complex or std::complex<double> We defer a c128 type (like std::complex<long double>) for a future RFC. Note that the references to C and C++ types above are simply explanatory. Nothing in this proposal assumes any particular high-level language type will map to the ab...

.... Users that wish to examine IR directly will see much less gobbbledygook and can more easily reason about the IR. Types ----- This proposal introduces new aggregate types to represent complex numbers. c16 - Complex of 16-bit float c32 - like float complex or std::complex<float> c64 - like double complex or std::complex<double> x86_c80 - Complex of x86_fp80 c128 - like long double complex or std::complex<long double> ppc_c128 - Complex of ppc_fp128 Note that the references to C and C++ types above are simply explanatory. Nothing in this proposal assumes...

.... Users that wish to examine IR directly will see much less gobbbledygook and can more easily reason about the IR. Types ----- This proposal introduces new aggregate types to represent complex numbers. c16 - Complex of 16-bit float c32 - like float complex or std::complex<float> c64 - like double complex or std::complex<double> x86_c80 - Complex of x86_fp80 c128 - like long double complex or std::complex<long double> ppc_c128 - Complex of ppc_fp128 Note that the references to C and C++ types above are simply explanatory. Nothing in this proposal assumes...

...ch less gobbbledygook and can more > easily reason about the IR. > > Types > ----- > > This proposal introduces new aggregate types to represent complex numbers. > > c16 - Complex of 16-bit float > c32 - like float complex or std::complex<float> > c64 - like double complex or std::complex<double> > x86_c80 - Complex of x86_fp80 > c128 - like long double complex or std::complex<long double> > ppc_c128 - Complex of ppc_fp128 > > Note that the references to C and C++ types above are simply explanatory. > No...

Hi! I want to know if a given element <- ('c64') is part of a vector<- ('c64', 'amiga', 'atari'). Does a function exist for this which gives back a logical value? thankx db

...Linux mail1.xxxxxx.xxx 2.6.18-238.9.1.el5PAE #1 SMP Tue Apr 12 18:52:55 EDT 2011 i686 i686 i386 GNU/Linux [root at mail1 paul]# cat /etc/issue CentOS release 5.6 (Final) Kernel \r on an \m Apr 24 10:26:24 mail1 snmpd[3493]: netsnmp_assert 1 == new_val->high failed int64.c:419 netsnmp_c64_check32_and_update() Apr 24 10:26:24 mail1 snmpd[3493]: netsnmp_assert 1 == new_val->high failed int64.c:419 netsnmp_c64_check32_and_update() Apr 24 10:26:54 mail1 snmpd[3493]: c64 32 bit check failed Apr 24 10:26:54 mail1 snmpd[3493]: netsnmp_assert 1 == new_val->high failed int64.c:419 n...

> The C55 and C64 builds diverge in exactly the same place as before (byte > 0x1000). The output from C55 build 11387 (svn head) diverges from C55 build > 11343 slightly later (byte 0x1116). Similarly, the output from C64 build > 11387 (svn head) diverges from C64 build 11343 slightly later (byte 0x112...

> misc.c provides the ability to override some functions, including the > allocation and printing. fftwrap.c uses speex_alloc, then calls > kiss_fftr_alloc, which calls kiss_fft_alloc, which calls KISS_FFT_MALLOC, > which is defined as malloc in kiss_fft.h. It would make it more consistent > to define KISS_FFT_MALLOC as speex_alloc. That is the only change that I > would

...anger with the summation of four > mults overflowing the 32 bit before the shift. > > I can fix this by accumulating each term into a long, but if the code scales > the x[],y[] vectors to avoid this problem I could use parallel 16x16 > multiply/adds. What do you mean here? The C64x has a _dotp2() instruction that does two 16x16 multiplies and adds the products together. Since the values are scaled to 16384, I can add the results of the two _dotp2()s together before the long add without worrying about overflow. I didn't understand that inner_prod() was always passed sca...

...root passwd geo exit exit reboot login to sl63 as 'geo' and 'root' ok. ran email, ran some web work. rebooted to centos, 'geo' and 'root' passwords refused, tried twice, booted centos dvd-1 in rescue mode, made same entries as with sl62. rebooted to c64, login to c64 as 'geo' and 'root' ok. rebooted to sl62, tried to login as 'geo' and 'root', nfw, refused. it is now a continuous cycle of repeating of above. any and all help, ideas, suggestions, will be greatly appreciated. tia. -- peace out. in a world with...

...n Mon, 1 Jul 2019 at 19:56, David Greene via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> llvm.creal.* - Overloaded intrinsic to extract the real part of a >> complex value >> declare float @llvm.creal.c32(c32 %Val) >> declare double @llvm.creal.c64(c64 %Val) > > What are your plans for the reverse? I assume we don't want the only > way to materialize a complex to be via memory so an insertvalue > equivalent (or maybe using insertvalue/extractvalue directly?) and a > literal value would probably be useful. Good points. Ori...

...nt, so it is not a burning issue for me. >> >> Try updating svn again. I just found out that EXTEND32() and EXTRACT16() >> were actually unsafe due to a pair of () missing around the argument. I >> also fixed a few minor things. Tell me if it works now. > > The C55 and C64 builds diverge in exactly the same place as before (byte > 0x1000). The output from C55 build 11387 (svn head) diverges from C55 > build 11343 slightly later (byte 0x1116). Similarly, the output from C64 > build 11387 (svn head) diverges from C64 build 11343 slightly later (byte >...

...bviously >> different, so it is not a burning issue for me. > > Try updating svn again. I just found out that EXTEND32() and EXTRACT16() > were actually unsafe due to a pair of () missing around the argument. I > also fixed a few minor things. Tell me if it works now. The C55 and C64 builds diverge in exactly the same place as before (byte 0x1000). The output from C55 build 11387 (svn head) diverges from C55 build 11343 slightly later (byte 0x1116). Similarly, the output from C64 build 11387 (svn head) diverges from C64 build 11343 slightly later (byte 0x1126). So, your c...

...for 128-bit FP might require also covering the 80-bit FP case. What long double means is, after all, a Clang issue and not an LLVM issue, but we figured that proposing more types would have a harder path to success than proposing fewer types. Do you think it's best to have the full set (c32, c64, c80, c128) or just (c32, c64, c128)? -Troy

.../usr/local/dovecot/etc/dovecot/dovecot.conf | # OS: Linux 2.6.35.14-106.fc14.i686.PAE i686 Fedora release 14 (Laughlin) ext3 | default_vsz_limit = 512 M | disable_plaintext_auth = no | first_valid_uid = 200 | last_valid_uid = 65534 | listen = * | lmtp_save_to_detail_mailbox = yes | login_greeting = c64.shuttle.de - IMAPs Service (dovecot) ready. | login_log_format_elements = %u %r %c | mail_location = maildir:/var/spool/mail/%u | mail_log_prefix = "%Us(%u,%r): " | mail_plugin_dir = /usr/dovecot/lib/dovecot/ | mail_plugins = " notify quota" | managesieve_notify_capability = mai...

.../dovecot/etc/dovecot/dovecot.conf | # OS: Linux 2.6.35.14-106.fc14.i686.PAE i686 Fedora release 14 (Laughlin) ext3 | auth_mechanisms = plain login | default_vsz_limit = 512 M | first_valid_uid = 200 | last_valid_uid = 65534 | listen = * | lmtp_save_to_detail_mailbox = yes | login_greeting = c64.shuttle.de - IMAPs Service (dovecot) ready. | login_log_format_elements = %u %r %c | mail_location = maildir:/var/spool/mail/%u | mail_log_prefix = "%Us(%u,%r): " | mail_plugin_dir = /usr/dovecot/lib/dovecot/ | mail_plugins = notify quota fts fts_squat | namespace inbox { | inbox...

...{ r: 0., i: 0. > } | ^ `libR_sys::Rcomplex` does not have this field | = note: > available fields are: `__bindgen_anon_1`, `private_data_c`| > and > |error[E0609]: no field `i` on type `libR_sys::Rcomplex` --> > extendr-api\src\scalar\rcplx_default.rs:105:35 | 105 | > Rcplx(c64::new(val.r, val.i)) | ^ unknown field | = note: available > fields are: `__bindgen_anon_1`, `private_data_c` help: one of the > expressions' fields has a field of the same name | 105 | > Rcplx(c64::new(val.r, val.__bindgen_anon_1.i)) | +++++++++++++++++| That seems like the generato...

...::Rcomplex` does not have this field > | > = note: available fields are: `__bindgen_anon_1`, `private_data_c` > > and > > error[E0609]: no field `i` on type `libR_sys::Rcomplex` > --> extendr-api\src\scalar\rcplx_default.rs:105:35 > | > 105 | Rcplx(c64::new(val.r, val.i)) > | ^ unknown field > | > = note: available fields are: `__bindgen_anon_1`, `private_data_c` > help: one of the expressions' fields has a field of the same name > | > 105 | Rcplx(c64::new(val.r, val....

...lot.new() scatterplot(dechway~dechr, reg.line=FALSE, smooth=TRUE, labels=F, boxplots='y', span=0.5, xlab="Time", ylab="Headway", ylim=c(0,9), data=headways) lines(headways$dechr, headways$schedule) A subset of the dataset I'm working with is at http://web.mit.edu/c64/www/headways.csv . The extra line, plotted with lines(), should be right at 4, but is actually below where it should be. I assume that I'm using the wrong function to plot this line, as there are many ways to do it, but have not the experience to know which function is appropriate to use wi...

...Type Comment --------- ---- ------- IPC$ IPC Externe IPC D$ Disk Standaard-share SharedDocs Disk print$ Disk Printerstuurprogramma's EPSONSty Printer EPSON Stylus C64 Series ADMIN$ Disk Beheer op afstand C$ Disk Standaard-share Domain=[IBM-SFN3] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager] Server Comment --------- ------- Workgroup Master -...