Return-Path: Delivered-To: diana@transocean.com Received: from vps.transocean.com by vps.transocean.com with LMTP id IMs0ISCrZ1rQVAAAInt2oQ for ; Tue, 23 Jan 2018 13:37:36 -0800 Return-path: Envelope-to: diana@transocean.com Delivery-date: Tue, 23 Jan 2018 13:37:36 -0800 Received: from boston.patriotpointe.com ([104.168.68.70]:55609) by vps.transocean.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89_1) (envelope-from ) id 1ee6Fv-0005dX-S0 for diana@transocean.com; Tue, 23 Jan 2018 13:37:36 -0800 From: Stopping Hair Loss Message-ID: Reply-To: stopping.hair.loss@patriotpointe.com To: diana@transocean.com MIME-Version: 1 Content-Type: multipart/alternative; boundary="hjdiuadyasd89ausda.hduasi89duyashd" Date: Tue, 23 Jan 2018 16:37:24 -0500 X-Spam-Status: Yes, score=3.6 X-Spam-Score: 36 X-Spam-Bar: +++ X-Spam-Report: Spam detection software, running on the system "vps.transocean.com", has identified this incoming email as possible spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see root\@localhost for details. Content preview: this you understand that it requires a redesign from the ground up, right? intel has their tick-tock cycle ? new design, then make it smaller, then a new design again, then make it smaller,? ? so it'll take until their next redesign. maybe [ice lake](en.wikipedia.org/wiki/ice_lake_(microarchitecture)), maybe the one after that. amd is currently less vulnerable, to they probably don't have to change so much. the rant is about spectre, which also affect amd and even arm, basically anything that is a [superscalar processor](en.wikipedia.org/wiki/superscalar_processor) nitpick: i think you're confusing superscale with speculative execution. superscale has nothing to do with this. the pentium 1 is superscalar (that's how it was a mive step up over the 486 at basically comparable clocks) but not susceptible to either vulnerability. both vulnerabilities depend on the combination of speculative execution and cpu caching (with meltdown requiring the additional mostly intel-specific wrinkle of access-deferred permission checking); speculation wasn't introduced to intel cpus until the pentium pro. i'm not entirely sure it would affect every superscalar processor: some cpus have used actual execution mode (supervisor mode) [...] Content analysis details: (3.6 points, 3.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: patriotpointe.com] 0.0 T_SPF_TEMPERROR SPF: test of record failed (temperror) -0.0 SPF_HELO_PASS SPF: HELO matches SPF record -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 0.0 HTML_MESSAGE BODY: HTML included in message 0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60% [score: 0.5024] 1.9 RAZOR2_CF_RANGE_51_100 Razor2 gives confidence level above 50% [cf: 100] 0.9 RAZOR2_CHECK Listed in Razor2 (http://razor.sf.net/) 0.0 T_REMOTE_IMAGE Message contains an external image X-Spam-Flag: YES Subject: ****SPAM**** Hairloss cure gets millions from the tank group --hjdiuadyasd89ausda.hduasi89duyashd Content-type: text/plain; charset="UTF-8" Content-transfer-encoding: 8bit this you understand that it requires a redesign from the ground up, right? intel has their tick-tock cycle ? new design, then make it smaller, then a new design again, then make it smaller,? ? so it'll take until their next redesign. maybe [ice lake](en.wikipedia.org/wiki/ice_lake_(microarchitecture)), maybe the one after that. amd is currently less vulnerable, to they probably don't have to change so much. the rant is about spectre, which also affect amd and even arm, basically anything that is a [superscalar processor](en.wikipedia.org/wiki/superscalar_processor) nitpick: i think you're confusing superscale with speculative execution. superscale has nothing to do with this. the pentium 1 is superscalar (that's how it was a mive step up over the 486 at basically comparable clocks) but not susceptible to either vulnerability. both vulnerabilities depend on the combination of speculative execution and cpu caching (with meltdown requiring the additional mostly intel-specific wrinkle of access-deferred permission checking); speculation wasn't introduced to intel cpus until the pentium pro. i'm not entirely sure it would affect every superscalar processor: some cpus have used actual execution mode (supervisor mode) More on ABC Shows () View on a web browser () http://diasud.patriotpointe.com/90d8saiujd read the story (http://diasud.patriotpointe.com/90d8saiujd) http://jdhas.patriotpointe.com/d9as8duipat0%2Fxc17I6tqFtt4w6DKMEqgHJqsNoRR6okA0xFhOD93lnQ%2BZji07V2P%2FzfH5hJw%2BcWbkCTs1SvJNT0ve9pO%2BJqA%3D%3Drio --hjdiuadyasd89ausda.hduasi89duyashd Content-Type: text/html; charset="UTF-8" Content-transfer-encoding: 8bit Investor Battle
More on ABC Shows View on a web browser
read the story
--hjdiuadyasd89ausda.hduasi89duyashd--