By: Brett (ggtgp.delete@this.yahoo.com), November 21, 2020 8:38 am
Room: Moderated Discussions
James (no.delete@this.thanks.invalid) on November 21, 2020 7:18 am wrote:
> Brett (ggtgp.delete@this.yahoo.com) on November 20, 2020 8:56 pm wrote:
>
> > But to go wider x86 decoding becomes expensive in area and
> > heat. x86 is stuck between a rock and a hard place, something has to give.
>
> Two obvious routes are keeping the decoder much as it is and making the L0 cache and
> the rest of the core wider, and adding decode hints to the L1 instruction cache.
Half the difference between Apple M1 and Intel may be 8 wide fetch of cold code.
You also have the issue that Apple is going fully 8 wide, you can’t do that with a 5GHz fireball.
To support a 8 wide pipeline you need 10-12 wide fetch, which rounds up to 16 wide fetch.
X86 decode is doomed.
> You could do either of those without breaking compatibility -- so history
> implies both Intel and AMD would want to do so if it was practical.
> Brett (ggtgp.delete@this.yahoo.com) on November 20, 2020 8:56 pm wrote:
>
> > But to go wider x86 decoding becomes expensive in area and
> > heat. x86 is stuck between a rock and a hard place, something has to give.
>
> Two obvious routes are keeping the decoder much as it is and making the L0 cache and
> the rest of the core wider, and adding decode hints to the L1 instruction cache.
Half the difference between Apple M1 and Intel may be 8 wide fetch of cold code.
You also have the issue that Apple is going fully 8 wide, you can’t do that with a 5GHz fireball.
To support a 8 wide pipeline you need 10-12 wide fetch, which rounds up to 16 wide fetch.
X86 decode is doomed.
> You could do either of those without breaking compatibility -- so history
> implies both Intel and AMD would want to do so if it was practical.
Topic | Posted By | Date |
---|---|---|
The next Apple chip | Maynard Handley | 2020/11/19 09:22 PM |
The next Apple chip | anon2 | 2020/11/19 09:59 PM |
The next Apple chip | Maynard Handley | 2020/11/20 10:45 AM |
The next Apple chip | Andrei F | 2020/11/20 01:47 AM |
The next Apple chip | dmcq | 2020/11/20 05:37 AM |
The next Apple chip | Andrei F | 2020/11/20 07:31 AM |
The next Apple chip | dmcq | 2020/11/20 10:57 AM |
The next Apple chip | Ronald Maas | 2020/11/20 09:54 AM |
The next Apple chip | Anon | 2020/11/20 12:30 PM |
The next Apple chip | Wes Felter | 2020/11/22 09:50 PM |
The next Apple chip | Maynard Handley | 2020/11/20 10:46 AM |
The next Apple chip | Jan Vlietinck | 2020/11/21 06:14 AM |
The next Apple chip | Doug S | 2020/11/21 09:34 AM |
The next Apple chip | Doug S | 2020/11/20 09:07 AM |
The next Apple chip | Maynard Handley | 2020/11/20 10:51 AM |
The next Apple chip | Doug S | 2020/11/20 12:07 PM |
The next Apple chip | Maynard Handley | 2020/11/20 12:54 PM |
The next Apple chip | Doug S | 2020/11/20 02:34 PM |
The next Apple chip | Richard S | 2020/11/20 06:38 PM |
The next Apple chip | David Hess | 2020/11/20 07:35 PM |
The next Apple chip | Brett | 2020/11/20 09:56 PM |
The next Apple chip | James | 2020/11/21 08:18 AM |
The next Apple chip | Brett | 2020/11/21 08:38 AM |
The next Apple chip | David Hess | 2020/11/21 08:17 PM |
The next Apple chip | Howard Chu | 2020/11/22 02:52 PM |
The next Apple chip | Brett | 2020/11/25 06:27 PM |
The next Apple chip | NaNon | 2020/11/21 04:01 AM |
The next Apple chip | Maynard Handley | 2020/11/21 11:30 AM |
The next Apple chip | David Hess | 2020/11/21 08:43 PM |
The next Apple chip | Jukka Larja | 2020/11/21 09:16 PM |
The next Apple chip | David Hess | 2020/11/21 09:47 PM |
The next Apple chip | Doug S | 2020/11/22 11:17 AM |
The next Apple chip | Jukka Larja | 2020/11/23 06:57 AM |
The next Apple chip | Maynard Handley | 2020/11/22 11:12 AM |
The next Apple chip | Jukka Larja | 2020/11/23 07:13 AM |
The next Apple chip | dmcq | 2020/11/23 09:18 AM |
The next Apple chip | Doug S | 2020/11/21 09:53 AM |
The next Apple chip | David Hess | 2020/11/21 08:40 PM |
The next Apple chip | Jacob Marley | 2020/11/21 12:40 PM |