Talk:ICL Series 39

Latest comment: 5 months ago by PaulBoddie in topic SX and S3L

Peripherals Cab 1 etc

edit

These were intended for the DM1 class systems. The Estriel has a separate FDS2500 disk cabinet — Preceding unsigned comment added by 82.2.221.189 (talk) 16:38, 21 March 2014 (UTC)Reply


SX and S3L

edit

The article describes SX as a mid-life upgrade to S3L. This is utterly incorrect - SX was a completely new design which had no components in common with S3L. Everything from the silicon technology to the cabinet was completely new. A member of the SX design team Glasguensis (talk) 16:08, 25 January 2010 (UTC)Reply

Amendments to improve/correct the article are welcome. It could do with a few references too - manuals, sales literature, technical journal etc sources. --TraceyR (talk) 23:06, 25 January 2010 (UTC)Reply

I too worked on Essex, it was a major development and is described in more detail here : http://www.fujitsu.com/ie/Images/ICL-Technical-Journal-v07i02.pdf — Preceding unsigned comment added by 81.187.109.41 (talk) 19:40, 18 January 2019 (UTC)Reply

I have reworded this now since the language was a bit ambiguous. I couldn't find any references to "S3X", though, so that was removed. Also, it seems that the DX models arrived in 1991, not 1993, but searching for DX is a challenge. --PaulBoddie (talk) 15:11, 30 May 2024 (UTC)Reply

edit

Cyberbot II has detected that page contains external links that have either been globally or locally blacklisted. Links tend to be blacklisted because they have a history of being spammed, or are highly innappropriate for Wikipedia. This, however, doesn't necessarily mean it's spam, or not a good link. If the link is a good link, you may wish to request whitelisting by going to the request page for whitelisting. If you feel the link being caught by the blacklist is a false positive, or no longer needed on the blacklist, you may request the regex be removed or altered at the blacklist request page. If the link is blacklisted globally and you feel the above applies you may request to whitelist it using the before mentioned request page, or request it's removal, or alteration, at the request page on meta. When requesting whitelisting, be sure to supply the link to be whitelisted and wrap the link in nowiki tags. The whitelisting process can take its time so once a request has been filled out, you may set the invisible parameter on the tag to true. Please be aware that the bot will replace removed tags, and will remove misplaced tags regularly.

Below is a list of links that were found on the main page:

  • http://www.cbronline.com/news/icls_series_39_sx_shows_it_has_nowt_to_learn_about_cpu_design_from_ibm_or_fujitsu
    Triggered by \bcbronline\.com\b on the local blacklist

If you would like me to provide more information on the talk page, contact User:Cyberpower678 and ask him to program me with more info.

From your friendly hard working bot.—cyberbot II NotifyOnline 19:01, 8 December 2013 (UTC)Reply

  Resolved This issue has been resolved, and I have therefore removed the tag, if not already done. No further action is necessary.—cyberbot II NotifyOnline 00:25, 4 March 2014 (UTC)Reply

  Resolved This issue has been resolved, and I have therefore removed the tag, if not already done. No further action is necessary.—cyberbot IITalk to my owner:Online 00:14, 4 July 2015 (UTC)Reply

Original C implementation on the ICL Series 39

edit

This is an interesting story from stack overflow. It discusses the size of C datatypes, and the intersection with ICL Series 39 architecture:

When we first implemented C on ICL Series 39 hardware, we took the standard at its word and mapped the data types to the natural representation on that machine architecture, which was short = 32 bits, int = 64 bits, long = 128 bits.

But we found that no serious C applications worked; they all assumed the mapping short = 16, int = 32, long = 64, and we had to change the compiler to support that.

Jeffrey Walton (talk) 07:49, 4 December 2020 (UTC)Reply

This is actually mentioned in the paper about VME-X:[1]: 478 

To be portable, a C application should not assume any particular size for arithmetic types, but experience suggests that the majority of applications do make such assumptions and will only work with the alternative mapping. Even applications which do not rely on the exact number of bits in a short or a long are often marred by assumptions about relative sizes (for instance, that two shorts can be packed into an int or that an extern declaration for a function returning a long can be omitted).

PaulBoddie (talk) 16:37, 25 May 2024 (UTC)Reply

References

  1. ^ Coates, P. (1993). "VME-X: Making VME Open" (PDF). ICL Technical Journal. ICL: 473. ISSN 0142-1557. Archived from the original (PDF) on 5 March 2016. Retrieved 7 November 2015.

"Initialisation and Support Application" listed at Redirects for discussion

edit

  An editor has identified a potential problem with the redirect Initialisation and Support Application and has thus listed it for discussion. This discussion will occur at Wikipedia:Redirects for discussion/Log/2022 September 28#Initialisation and Support Application until a consensus is reached, and readers of this page are welcome to contribute to the discussion. MB 03:09, 28 September 2022 (UTC)Reply