search for: 64's

...r the constant expression division case, since the division by zero expression would be folded away leaving only a call to trap. The performance penalty for using -fsanitize on other non-constant division expressions is still unclear to me; and concerning. Although, I've been contemplating x86-64's behaviour for this case when floating point traps are disabled. Ideally, the compiler should preserve that behaviour, which might make this software implementation messy. Especially if different processors have different implementations. The simplest solution... let the hardware behave as it...

...me; and concerning. If the performance penalty is unclear to you, that means you haven't measured it. Until you measure, you have absolutely no business complaining about a potential performance problem. Measure, and then come back with numbers. > Although, I've been contemplating x86-64's behaviour for this case when > floating point traps are disabled. Ideally, the compiler should preserve > that behaviour, which might make this software implementation messy. > Especially if different processors have different implementations. The > simplest solution... let the ha...

Hi folks, Anyway, I have a main development system which is P4 based (without EM64T) and a dozen diskless Athlon 64's. I'd like to be able to compile kernel's, etc for the Athlons in x86_64 bit mode. Any idea how to arrange this? I've recompiled the src.rpm for binutils (added a single line "CARGS=--enable-targets=x86_64-linux" to the specfile) an...

...Buffer overflow - unable to expand buffer by 36 bytes. regfio_rootkey: corrupt registry file ? No root key record located Could not get rootkey Any ideas anyone? Has the format of the NTUSER.DAT changed, and if so which one do I need to use? Jobst -- It took the power of 3 Commodore 64's to go to the moon, but it takes a 2GHz Pentium 4 to run XP... Something is desperately wrong here! | |0| | Jobst Schmalenbach, jobst at barrett.com.au, General Manager | | |0| Barrett Consulting Group P/L & The Meditation Room P/L |0|0|0| +61 3 9532 7677, POBox 277, Caulfield...

On Sat, Apr 6, 2013 at 10:07 AM, Cameron McInally <cameron.mcinally at nyu.edu> wrote: > 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

...f my assumptions are incorrect. Our team's culture dictates that "an instruction is an instruction", hence a performance problem. I understand that "performance problem" will have different definitions among different tribes. > Although, I've been contemplating x86-64's behaviour for this case when > > floating point traps are disabled. Ideally, the compiler should preserve > > that behaviour, which might make this software implementation messy. > > Especially if different processors have different implementations. The > > simplest so...

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