- Joined
- Apr 9, 2018
- Messages
- 96 (0.16/day)
I recall reading about Itanium in the early days, it seems like ever since it's inception it has been a myth at the best of times.
System Name | BY-2015 |
---|---|
Processor | Intel Core i7-6700K (4 x 4.00 GHz) w/ HT and Turbo on |
Motherboard | MSI Z170A GAMING M7 |
Cooling | Scythe Kotetsu |
Memory | 2 x Kingston HyperX DDR4-2133 8 GiB |
Storage | Crucial MX300 275 GB, Seagate Exos X12 TB 7200 RPM |
Display(s) | Samsung SyncMaster T240 24" LCD (1920x1200 HDMI) + Samsung SyncMaster 906BW 19" LCD (1440x900 VGA) |
Case | Coolermaster HAF 932 w/ USB 3.0 5.25" bay |
Audio Device(s) | Realtek ALC1150, Micca OriGen+ |
Power Supply | Enermax Platimax 850w |
Mouse | SteelSeries Sensei RAW |
Keyboard | Tesoro Excalibur |
Software | Windows 10 Pro 64-bit |
Benchmark Scores | Faster than the tortoise; slower than the hare. |
It could have been but Intel gave up on it a long time ago. It uses a lot fewer transistors to execute a task than x86 does. It left most optimizations to the software and compiler rather than processor itself.I don't recall them having any Itanium version even close to efficient enough to consider that.
System Name | Darkside |
---|---|
Processor | i7 3770K |
Motherboard | GA-Z77X-UD5H |
Cooling | Zalman CNPS20LQ with 2x Corsair SP120 |
Memory | Patriot Viper Xtreme 16GB 1866MHz |
Video Card(s) | Gigabyte GTX 1080 |
Storage | many |
Display(s) | Samsung C27JG5x |
Case | Corsair Vengeance C70 (Arctic white) |
Audio Device(s) | iFi xDSD |
Power Supply | EVGA 750W G2 |
Mouse | Corsair M65 |
Keyboard | Corsair K70 LUX RGB |
Benchmark Scores | Not sure, don't care |
System Name | More hardware than I use :| |
---|---|
Processor | 4.7 8350 - 4.2 4560K - 4.4 4690K |
Motherboard | Sabertooth R2.0 - Gigabyte Z87X-UD4H-CF - AsRock Z97M KIller |
Cooling | Mugen 2 rev B push/pull - Hyper 212+ push/pull - Hyper 212+ |
Memory | 16GB Gskill - 8GB Gskill - 16GB Ballistix 1.35v |
Video Card(s) | Xfire OCed 7950s - Powercolor 290x - Oced Zotac 980Ti AMP! (also have two 7870s) |
Storage | Crucial 250GB SSD, Kingston 3K 120GB, Sammy 1TB, various WDs, 13TB (actual capactity) NAS with WDs |
Display(s) | X-star 27" 1440 - Auria 27" 1440 - BenQ 24" 1080 - Acer 23" 1080 |
Case | Lian Li open bench - Fractal Design ARC - Thermaltake Cube (still have HAF 932 and more ARCs) |
Audio Device(s) | Titanium HD - Onkyo HT-RC360 Receiver - BIC America custom 5.1 set up (and extra Klipsch sub) |
Power Supply | Corsair 850W V2 - EVGA 1000 G2 - Seasonic 500 and 600W units (dead 750W needs RMA lol) |
Mouse | Logitech G5 - Sentey Revolution Pro - Sentey Lumenata Pro - multiple wireless logitechs |
Keyboard | Logitech G11s - Thermaltake Challenger |
Software | I wish I could kill myself instead of using windows (OSX can suck it too). |
HP spent billions trying to keep itanic afloat with intel...HP is dumb with a long history of blowing cash lolSuck Eggs HP.
You bought Compaq and killed Alpha
Now your Itanic has sunk.
Processor | Ryzen 5 3600 |
---|---|
Motherboard | MSI B450 Tomahawk ATX |
Cooling | Scythe Kotetsu with AM4 bracket |
Memory | PNY Anarchy-X XLR8 Red DDR4 3200 MHz C15-17-17-17-35 |
Video Card(s) | MSI GeForce RTX 2060 GAMING Z 6G |
Storage | Samsung 970 EVO NVMe M.2 500 GB, SanDisk Ultra II 480 GB |
Display(s) | Samsung SyncMaster C27H711 OC refresh rate 110Hz |
Case | Phantek Eclipse P400S (PH-EC416PS) |
Audio Device(s) | EVGA NU Audio |
Power Supply | EVGA 850 BQ |
Mouse | SteelSeries Rival 310 |
Keyboard | Logitech G G413 Silver |
Software | Windows 10 Professional 64-bit v1903 |
Actually the intellectual property of Alpha was bought by Intel.You bought Compaq and killed Alpha![]()
System Name | BY-2015 |
---|---|
Processor | Intel Core i7-6700K (4 x 4.00 GHz) w/ HT and Turbo on |
Motherboard | MSI Z170A GAMING M7 |
Cooling | Scythe Kotetsu |
Memory | 2 x Kingston HyperX DDR4-2133 8 GiB |
Storage | Crucial MX300 275 GB, Seagate Exos X12 TB 7200 RPM |
Display(s) | Samsung SyncMaster T240 24" LCD (1920x1200 HDMI) + Samsung SyncMaster 906BW 19" LCD (1440x900 VGA) |
Case | Coolermaster HAF 932 w/ USB 3.0 5.25" bay |
Audio Device(s) | Realtek ALC1150, Micca OriGen+ |
Power Supply | Enermax Platimax 850w |
Mouse | SteelSeries Sensei RAW |
Keyboard | Tesoro Excalibur |
Software | Windows 10 Pro 64-bit |
Benchmark Scores | Faster than the tortoise; slower than the hare. |
Before AMD64 rolled out, IA-64 made a lot of sense as the future of computing. It still does in some regards but people would rather have backwards compatibility in processors than an instruction set for the 21st century.HP spent billions trying to keep itanic afloat with intel...HP is dumb with a long history of blowing cash lol
Their execs were all having too many drug parties at intel, apparently. You'd have to be higher than a weather balloon to invest in itanium.
System Name | More hardware than I use :| |
---|---|
Processor | 4.7 8350 - 4.2 4560K - 4.4 4690K |
Motherboard | Sabertooth R2.0 - Gigabyte Z87X-UD4H-CF - AsRock Z97M KIller |
Cooling | Mugen 2 rev B push/pull - Hyper 212+ push/pull - Hyper 212+ |
Memory | 16GB Gskill - 8GB Gskill - 16GB Ballistix 1.35v |
Video Card(s) | Xfire OCed 7950s - Powercolor 290x - Oced Zotac 980Ti AMP! (also have two 7870s) |
Storage | Crucial 250GB SSD, Kingston 3K 120GB, Sammy 1TB, various WDs, 13TB (actual capactity) NAS with WDs |
Display(s) | X-star 27" 1440 - Auria 27" 1440 - BenQ 24" 1080 - Acer 23" 1080 |
Case | Lian Li open bench - Fractal Design ARC - Thermaltake Cube (still have HAF 932 and more ARCs) |
Audio Device(s) | Titanium HD - Onkyo HT-RC360 Receiver - BIC America custom 5.1 set up (and extra Klipsch sub) |
Power Supply | Corsair 850W V2 - EVGA 1000 G2 - Seasonic 500 and 600W units (dead 750W needs RMA lol) |
Mouse | Logitech G5 - Sentey Revolution Pro - Sentey Lumenata Pro - multiple wireless logitechs |
Keyboard | Logitech G11s - Thermaltake Challenger |
Software | I wish I could kill myself instead of using windows (OSX can suck it too). |
Low performance = failure no matter what.Before AMD64 rolled out, IA-64 made a lot of sense as the future of computing. It still does in some regards but people would rather have backwards compatibility in processors than an instruction set for the 21st century.
System Name | SolarwindMobile |
---|---|
Processor | AMD FX-9800P RADEON R7, 12 COMPUTE CORES 4C+8G |
Motherboard | Acer Wasp_BR |
Cooling | It's Copper. |
Memory | 2 x 8GB SK Hynix/HMA41GS6AFR8N-TF |
Video Card(s) | ATI/AMD Radeon R7 Series (Bristol Ridge FP4) [ACER] |
Storage | TOSHIBA MQ01ABD100 1TB + KINGSTON RBU-SNS8152S3128GG2 128 GB |
Display(s) | ViewSonic XG2401 SERIES |
Case | Acer Aspire E5-553G |
Audio Device(s) | Realtek ALC255 |
Power Supply | PANASONIC AS16A5K |
Mouse | SteelSeries Rival |
Keyboard | Ducky Channel Shine 3 |
Software | Windows 10 Home 64-bit (Version 1607, Build 14393.969) |
HPHP spent billions trying to keep itanic afloat with intel...HP is dumb with a long history of blowing cash lol
Their execs were all having too many drug parties at intel, apparently. You'd have to be higher than a weather balloon to invest in itanium.
Either way intel HP created the Itanic ....Actually the intellectual property of Alpha was bought by Intel.
System Name | BY-2015 |
---|---|
Processor | Intel Core i7-6700K (4 x 4.00 GHz) w/ HT and Turbo on |
Motherboard | MSI Z170A GAMING M7 |
Cooling | Scythe Kotetsu |
Memory | 2 x Kingston HyperX DDR4-2133 8 GiB |
Storage | Crucial MX300 275 GB, Seagate Exos X12 TB 7200 RPM |
Display(s) | Samsung SyncMaster T240 24" LCD (1920x1200 HDMI) + Samsung SyncMaster 906BW 19" LCD (1440x900 VGA) |
Case | Coolermaster HAF 932 w/ USB 3.0 5.25" bay |
Audio Device(s) | Realtek ALC1150, Micca OriGen+ |
Power Supply | Enermax Platimax 850w |
Mouse | SteelSeries Sensei RAW |
Keyboard | Tesoro Excalibur |
Software | Windows 10 Pro 64-bit |
Benchmark Scores | Faster than the tortoise; slower than the hare. |
Only benchmark I could find:Low performance = failure no matter what.
There is no reason for making a 128-bit ISA, at least not yet anyway. Current x86 architectures have partial support for up to 512-bit through AVX, which for the time being is a much more flexible and smart way of getting good performance without adding massive complexity to the design. I see no reason why the entire core should be extended to 128-bit, at least not for the next decade.Then, in a couple months Itanic revives as IA-128 and has partial compatibility with RISC-V.
Processor | i5-8400 |
---|---|
Motherboard | ASUS ROG STRIX Z370-I GAMING |
Cooling | Alpenföhn Black Ridge |
Memory | 2*16GB DDR4-3200 CL16 |
Video Card(s) | Gainward GeForce RTX 2080 Phoenix |
Storage | 1TB Samsung 970 Pro, 2TB Intel 660p |
Display(s) | ASUS PG279Q, Eizo EV2736W |
Case | Dan Cases A4-SFX |
Power Supply | Corsair SF600 |
Mouse | Logitech G700 |
Keyboard | Corsair K60 |
You are confusing register width with address width.64-bit calculations were largely a secondary concern. Move to 64-bit was largely dictated by memory - more specifically address space - of 32-bit becoming too small.
Processor | i5-8400 |
---|---|
Motherboard | ASUS ROG STRIX Z370-I GAMING |
Cooling | Alpenföhn Black Ridge |
Memory | 2*16GB DDR4-3200 CL16 |
Video Card(s) | Gainward GeForce RTX 2080 Phoenix |
Storage | 1TB Samsung 970 Pro, 2TB Intel 660p |
Display(s) | ASUS PG279Q, Eizo EV2736W |
Case | Dan Cases A4-SFX |
Power Supply | Corsair SF600 |
Mouse | Logitech G700 |
Keyboard | Corsair K60 |
To have register width lower than address width requires more operations, but is not uncommon. Nearly all the early computers did this, Intel 8086 16-bit register width 20-bit address width, 80286 was 16-bit / 24-bit addressing. MOS 6502 was a 8-bit CPU with 16-bit addressing, used in Commodore 64, Atari 2600, Apple II, NES and many more.Addresses have a tendency to go through integer units for various purposes, address generation for example. They are not directly related but eventually they collide.
PAE is a workaround. It is often not enough and has downsides, not least of which is enabling support for it on every level.
Processor | i5-8400 |
---|---|
Motherboard | ASUS ROG STRIX Z370-I GAMING |
Cooling | Alpenföhn Black Ridge |
Memory | 2*16GB DDR4-3200 CL16 |
Video Card(s) | Gainward GeForce RTX 2080 Phoenix |
Storage | 1TB Samsung 970 Pro, 2TB Intel 660p |
Display(s) | ASUS PG279Q, Eizo EV2736W |
Case | Dan Cases A4-SFX |
Power Supply | Corsair SF600 |
Mouse | Logitech G700 |
Keyboard | Corsair K60 |
With drive for efficiency and simultaneously widening the compute the different address width (at least to the larger side) seem to be uncommon in current architectures, no?To have register width lower than address width requires more operations, but is not uncommon. Nearly all the early computers did this, Intel 8086 16-bit register width 20-bit address width, 80286 was 16-bit / 24-bit addressing. MOS 6502 was a 8-bit CPU with 16-bit addressing, used in Commodore 64, Atari 2600, Apple II, NES and many more.
System Name | Kratos |
---|---|
Processor | Intel Core i7 3930k @ 4.75Ghz |
Motherboard | ASUS P9X79 Deluxe |
Cooling | Corsair H100i V2 |
Memory | G.Skill DDR3-2133, 16gb (4x4gb) @ 9-11-10-28-108-1T 1.65v |
Video Card(s) | Sapphire AMD Radeon RX Vega 64 |
Storage | 2x120Gb SATA3 SSD Raid-0, 4x1Tb RAID-5, 1x500GB, 1x512GB Samsung 960 Pro NVMe |
Display(s) | 1x LG 27UD69P (4k), 2x Dell S2340M (1080p) |
Case | Antec 1200 |
Audio Device(s) | Onboard Realtek® ALC898 8-Channel High Definition Audio |
Power Supply | Seasonic 1000-watt 80 PLUS Platinum |
Mouse | Logitech G602 |
Keyboard | Rosewill RK-9100 |
Software | Ubuntu 18.04 (5.3.0 Mainline Kernel) |
Benchmark Scores | Benchmarks aren't everything. |
A lot of that came from the fact that the compilers had to do all the hard work. Little do people know but in your common x86-64 chip there's a lot of optimization of the CPU instructions going on behind the scenes at the silicon level before even one instruction is executed. There was none of that happening with Itanium, all of that had to be done at the compiler level which they generally weren't able to do.
Actually, it did. It's not easy to write a compiler to take advantage of 128 general-purpose registers in an effective way for every workload imaginable. x86 only had 8 and x86-64 bumped that to 16. Theoretically it could be really fast, but it can only be as fast as the compiler and how it determines what data goes where. The nice thing with having a bunch of general-purpose registers is because you don't need to load and store data to and from memory as often and accessing registers is faster than accessing cache, however, there are consequences to getting evicted from registers incorrectly which is more and more likely as you have to manage a larger number of registers. The reality is that you can only look so far ahead so, I suspect that a lot of the time those registers are getting loaded and stored far more often then they should be, mainly because you have to figure it out ahead of time if some data is going to be used soon or way later and the cost of getting that wrong is significant.Actually not. Itanium features explicit parallel instructions, and compilers are limited to working with just a few instructions within a scope, there is no way a compiler could be able to properly structure the code and memory to leverage this. It's kind of similar to SIMD(like AVX), the compiler can vectorize small patterns of a few instructions, but can never restructure larger code, so if you want proper utilization of SIMD you need to use intrinsics which are basically mapped directly to assembly. No compiler will ever be able to do this automatically.
I didn't quite get that one.With drive for efficiency and simultaneously widening the compute the different address width (at least to the larger side) seem to be uncommon in current architectures, no?
I haven't run any Windows in 32-bit since XP, but from what I've read does NX bit require it, which is enabled on all modern operating systems for security reasons.I remember PAE very well. It needed support from motherboard, BIOS, operating system and depending on circumstances, application. That was a lot of fun
Are you sure about 32-bit Windows 8 and 10 requiring PAE? They do support it and can benefit from it but I remember trying to turn on PAE manually on Windows 8 (and failing due to stupid hardware).
The problem from the compiler side is that the code, regardless of language, needs to be structured in a way that the compiler can basically saturate these resources.Actually, it did. It's not easy to write a compiler to take advantage of 128 general-purpose registers in an effective way for every workload imaginable.
In theory, having many registers is beneficial. At machine code level, x86 code does a lot of moving around between registers (which usually is completely wasted cycles, ARM does a lot more…). So having more registers (even if only on the ISA level) can eliminate operations and therefore be beneficial, I have no issues so far.x86 only had 8 and x86-64 bumped that to 16. Theoretically it could be really fast, but it can only be as fast as the compiler and how it determines what data goes where. The nice thing with having a bunch of general-purpose registers is because you don't need to load and store data to and from memory as often and accessing registers is faster than accessing cache<snip>
Processor | Intel i5-6600k (AMD Ryzen5 3600 in a box, waiting for a mobo) |
---|---|
Motherboard | ASRock Z170 Extreme7+ |
Cooling | Arctic Cooling Freezer i11 |
Memory | 2x16GB DDR4 3600 G.Skill Ripjaws V (@3200) |
Video Card(s) | EVGA GTX 1060 SC |
Storage | 500GB Samsung 970 EVO, 500GB Samsung 850 EVO, 1TB Crucial MX300 and 3TB Seagate |
Display(s) | HP ZR24w |
Case | Raijintek Thetis |
Audio Device(s) | Audioquest Dragonfly Red :D |
Power Supply | Seasonic 620W M12 |
Mouse | Logitech G502 Proteus Core |
Keyboard | G.Skill KM780R |
Software | Arch Linux + Win10 |
It doesn't really matter if you try to execute both branches of a conditional, or you do speculative execution. Either way you're pretty much screwed after three or more conditionals coming within a few instructions, as the problem grows exponentially.For example, you what happens with x86/x86-64 when it tries to speed up code execution? It tries to predict whether a code path will be chosen and execute it ahead of time using idle resources. The problem is if it turns out the prediction was wrong, the pipeline has to be flushed and new instructions brought in. You know what Itanium does/did? It doesn't try to predict anything, it will execute both branches of a conditional statement and pick whichever is needed when the time comes.
Processor | Intel i5-6600k (AMD Ryzen5 3600 in a box, waiting for a mobo) |
---|---|
Motherboard | ASRock Z170 Extreme7+ |
Cooling | Arctic Cooling Freezer i11 |
Memory | 2x16GB DDR4 3600 G.Skill Ripjaws V (@3200) |
Video Card(s) | EVGA GTX 1060 SC |
Storage | 500GB Samsung 970 EVO, 500GB Samsung 850 EVO, 1TB Crucial MX300 and 3TB Seagate |
Display(s) | HP ZR24w |
Case | Raijintek Thetis |
Audio Device(s) | Audioquest Dragonfly Red :D |
Power Supply | Seasonic 620W M12 |
Mouse | Logitech G502 Proteus Core |
Keyboard | G.Skill KM780R |
Software | Arch Linux + Win10 |
It should work ok for the small instruction windows that fits into the pipeline at any given moment. But I'm just speculating (see what I did there?).It doesn't really matter if you try to execute both branches of a conditional, or you do speculative execution. Either way you're pretty much screwed after three or more conditionals coming within a few instructions, as the problem grows exponentially.
Yeah, there's never going to be a universal fix for this. Just more or less efficient solutions spread between the compiler and the CPU.One of the fundamental problems for CPUs is that the CPU have less context than the author of the code does.
Processor | Intel i5-6600k (AMD Ryzen5 3600 in a box, waiting for a mobo) |
---|---|
Motherboard | ASRock Z170 Extreme7+ |
Cooling | Arctic Cooling Freezer i11 |
Memory | 2x16GB DDR4 3600 G.Skill Ripjaws V (@3200) |
Video Card(s) | EVGA GTX 1060 SC |
Storage | 500GB Samsung 970 EVO, 500GB Samsung 850 EVO, 1TB Crucial MX300 and 3TB Seagate |
Display(s) | HP ZR24w |
Case | Raijintek Thetis |
Audio Device(s) | Audioquest Dragonfly Red :D |
Power Supply | Seasonic 620W M12 |
Mouse | Logitech G502 Proteus Core |
Keyboard | G.Skill KM780R |
Software | Arch Linux + Win10 |
There was something definitely wrong with execution, it wasn't just the product. Look at ARM and how they had no trouble jumpstarting a new architecture from scratch. Ironically, one that has grown to 64 bits, too.Maybe future will eventually get to that, but I think it was product simply too much ahead of its time.
Bit like tessellation in R9800 Pro.![]()