|
|
Vacation. For one more week. Then I need a vacation.
Thanks,
Sean Ewington
CodeProject
|
|
|
|
|
Updating the Kent AI is on Blizzard time.
modified 23-May-23 16:10pm.
|
|
|
|
|
This is why I don't allow my HP printers to access the internet. They can't download the crapware HP is pushing as firmware.
|
|
|
|
|
Interestingly, many of the newer HP printers "will not print" if they cannot phone home. Looking at my fairly recent Brother laser that does what I want it to do - print. The HP is in the trashcan, as I opted out of participating in HP's attempt to monitize their dying brand.
Charlie Gilley
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
Has never been more appropriate.
|
|
|
|
|
[^] I've used PostSharp in the past years, and like the concepts of Aspect Oriented Programming (AOP) ... handling application "cross cutting" code concerns once, avoiding rewriting boilerplate, etc.
Metalama ... see the features coverage in the link ... appears to take that significantly further in terms of integration with VS, Roslyn compilers, LINQ, the ability to save/view/debug either your original aspect-annotated code ... or, the code that will actually run after compile time "expansion" of the aspects.
Full disclosure: I had a comp copy of PostSharp for a few years, thanks to Gael Freitur (founder) who patiently handled some questions from me I now realize were quite naive 
selected AOP references: [^], [^], [^]
Also, check out use of AOP in other tools: Frody, Spring, etc., which I have never used.
p.s. nice to be back here in a limited way with eyesight improved/improving
«The mind is not a vessel to be filled but a fire to be kindled» Plutarch
modified 23-May-23 8:53am.
|
|
|
|
|
Among Intel's expressed benefits for a 64-bit mode-only architecture is removing ring 1 and 2, dropping 16-bit addressing support, eliminating ring 3 I/O port accesses and the string port I/O, simplified segmentation model, and removing some unused operating system bits.
Under this proposal, those wanting to run legacy 32-bit operating systems would have to rely on virtualization. To further clarify, 32-bit x86 user-space software would continue to work on modern 64-bit operating systems with X86-S.
The biggest question I have at this point is how much die area and microcode space would this actually save.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
|
|
|
|
|
I don't know how much die area or microcode space it would save (has the 16-bit 80x86 microcode changed since the 80286?), but it would eliminate a large number of states and operations that must today be verified in any regression tests for new CPUs.
These CPUs would presumably be unsuitable for running 16-bit code (unless the hypervisor provides full emulation), but how many of us actually do so, these days? If Intel can reduce costs by redesigning the chip in a way that 99% of us won't notice - go for it!
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Intel might as well remove the 32-bit instructions to save more die area and give us more processor cores. 64-bit Linux does not allow running of 32-bit applications.
|
|
|
|
|
64-bit Windows does allow 32-bit applications. There are a lot of 32-bit applications still running on Windows desktops. What there aren't running is 16-bit applications.
|
|
|
|
|
Is that why Turbo BASIC won't run on Win 10? 
|
|
|
|
|
Is Turbo Basic a 16 bit program? If so it won't run on any 64 bit version of Windows, include XP 64, Vista 64, 7 64, 8.x 64, or any of the 64 bit versions of Windows Server. Microsoft expressly depreciated 16 bit applications for 64 bit Windows.
|
|
|
|
|
I read Intel's white paper on this change. The impacts are as follows:
- No more starting the processor in real mode and then shifting to protected mode before OS loading. Instead, the processor starts in protected mode.
- Elimination of original X86 level machine instructions. To my knowledge no 64-bit OS supports 16-bit applications.
- Elimination/streamlining of some exceptions, including stack overflow and underflow. These will still be checked for but won't be separate exceptions.
- 32-bit code will still be supported via virtualization. This will be hardware level support, including the IA32 instruction set, so there is minimal performance impact.
- Improved processor level security by eliminating attack surface and simplifying the hardware design.
- Near complete elimination of the segment:offset addressing scheme. This scheme will still be there but will require OS level calls to change the segment register. For applications this will result in a flat address space.
- Will require a 64-bit OS.
|
|
|
|
|
I wonder how frequently used the IA-32 instruction set is. It seems that removing it would save even more silicon real estate.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
There are still plenty of 32-bit applications out there (at least in the Windows world).
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
I was mistaken. I thought IA-32 referred to the Itanium's instruction set but it is their term for the thirty-bit version of X86 instructions.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
On workstations, there is a lot of legacy IA-32 code, including all versions of Visual Studio prior to VS 2022. Not so much on the server side anymore.
|
|
|
|
|
As I wrote, Quote: I was mistaken. I thought IA-32 referred to the Itanium's instruction set but it is their term for the thirty-bit version of X86 instructions.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
"When they came for the 16-bitness I said nothing, for I did not use 16-bit code..."
|
|
|
|
|
Wondering how that might affect the effort to port OpenVMS to X86...
|
|
|
|
|
I think it would simplify the VMS port since the OS won't have to deal with 32 bit code. Remember, VMS is a 64 bit OS.
|
|
|
|
|
Well, most likely this version will be of course, but I have this MicroVAX... 
|
|
|
|
|
|
I just received an E-mail announcing that the X86-64 port of OpenVMS is ready for people to try it out.
I may have to look into the system requirements.
|
|
|
|
|
Virgin Galactic's lengthy road to space tourism is nearing an end. The firm now expects its final VSS Unity test flight to launch as soon as May 25th at 10AM Eastern, with specialist training starting on May 22nd. Dear investors, yes we are bleeding money, but a Virgin Galactic ticket costs $450,000 with a $150,000 deposit. You know, if this test flight is successful.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
