search for: err_handler

...e of being accepted. (Although I'm not intimately familiar with the implementation, so there could be some subtlety that would prevent it.) You might need to do this in the processor-specific backend to avoid other undefined-behavior-based optimizations—that is, recognize "if (x == 0) goto err_handler; else y/x;" and replace it with "register-pc-in-fp-handler-map(); turn-on-fp-traps(); y/x;". Jeffrey

...ly if different processors have different implementations. The simplest solution... let the hardware behave as it should. > You might need to > do this in the processor-specific backend to avoid other > undefined-behavior-based optimizations—that is, recognize "if (x == 0) > goto err_handler; else y/x;" and replace it with > "register-pc-in-fp-handler-map(); turn-on-fp-traps(); y/x;". > I believe that the constant folder would remove the constant division by zero and conditional before the backend could have its say. We would be left with only the jump to the erro...

...make code in general run slower, so that you can get a particular behavior on some CPUs in unusual cases. >> You might need to >> do this in the processor-specific backend to avoid other >> undefined-behavior-based optimizations—that is, recognize "if (x == 0) >> goto err_handler; else y/x;" and replace it with >> "register-pc-in-fp-handler-map(); turn-on-fp-traps(); y/x;". > > > I believe that the constant folder would remove the constant division by > zero and conditional before the backend could have its say. We would be left > with on...

Hey Owen, Thanks for your reply. I definitely understand your perspective. Hopefully I can change it. }:-) On Sat, Apr 6, 2013 at 1:18 AM, Owen Anderson <resistor at mac.com> wrote: ... > As I've pointed out, clang does provide such functionality as an opt-in > feature through its -fsanitize options. A hypothetical Fortran frontend > could do the same, and even make it an

Both of our production asterisk servers are dumping core when making writes to our cdr tables. Here is a backtrace of the problems we are having: #0 0x00447b1f in tdserror (tds_ctx=0x1, tds=0xb7938c90, msgno=20004, errnum=9) at util.c:347 347 if (tds_ctx && tds_ctx->err_handler) { (gdb) bt #0 0x00447b1f in tdserror (tds_ctx=0x1, tds=0xb7938c90, msgno=20004, errnum=9) at util.c:347 #1 0x0045c6d6 in goodread (tds=0xb7938c90, buf=0x2abb220 "?\033F", buflen=8) at net.c:501 #2 0x0045c765 in tds_read_packet (tds=0xb7938c90) at net.c:567 #3 0x004496bf in tds_get_by...

Looks like the GSO is involved? I got this while running Dom0 only (no guests), with a BOINC/Rosetta@home application running on all 4 cores. changeset: 10649:8e55c5c11475 Build: x86_32p (pae). ------------[ cut here ]------------ kernel BUG at net/core/dev.c:1133! invalid opcode: 0000 [#1] SMP CPU: 0 EIP: 0061:[<c04dceb0>] Not tainted VLI EFLAGS: 00210297 (2.6.16.13-xen

...program's performance improved 20x!, but the results aren't correct". :) > >> You might need to > >> do this in the processor-specific backend to avoid other > >> undefined-behavior-based optimizations—that is, recognize "if (x == 0) > >> goto err_handler; else y/x;" and replace it with > >> "register-pc-in-fp-handler-map(); turn-on-fp-traps(); y/x;". > > > > > > I believe that the constant folder would remove the constant division by > > zero and conditional before the backend could have its say. We w...

Greetings, Following patches are intended to support SR-IOV capability in the Linux kernel. With these patches, people can turn a PCI device with the capability into multiple ones from software perspective, which will benefit KVM and achieve other purposes such as QoS, security, and etc. The Physical Function and Virtual Function drivers using the SR-IOV APIs will come soon! Major changes from

Greetings, Following patches are intended to support SR-IOV capability in the Linux kernel. With these patches, people can turn a PCI device with the capability into multiple ones from software perspective, which will benefit KVM and achieve other purposes such as QoS, security, and etc. The Physical Function and Virtual Function drivers using the SR-IOV APIs will come soon! Major changes from

Greetings, Following patches are intended to support SR-IOV capability in the Linux kernel. With these patches, people can turn a PCI device with the capability into multiple ones from software perspective, which will benefit KVM and achieve other purposes such as QoS, security, and etc. The Physical Function and Virtual Function drivers using the SR-IOV APIs will come soon! Major changes from