#gcc

21 posts · Last used 12d

A friend of the #gcobol (#gcc #cobol) project sent us an anthill of code (62Kloc of COBOL and 6Kloc of copybooks) that doesn't compile. Jim's got fixes for some of the problems and we're cataloging the rest. The team's been waiting for some "real code" so this is very exciting! Happy to chat about looking at yours!
0
0
0
0
🟢 Diplomatic Statement | 4/10 🇮🇷 🇺🇸 Iran calls US-GCC statement interventionist Iran's Foreign Ministry called the joint statement by the US Secretary of State and GCC foreign ministers 'interventionist, irresponsible, and provocative,' warning against continued hostile interference in the region. #OSINT #NewsGroup #Iran #USA #GCC
0
0
0
0
Times of India | Cloud-first, AI-led GCC reimagines global banking AI generated summary, Read the full article for complete information. The article explains how Citizens Bank, in partnership with Cognizant, is turning its Hyderabad global capability centre (GCC) from a traditional offshore delivery unit into a cloud‑first, AI‑led transformation engine that owns platforms, capabilities, and business outcomes. Built under a “build‑operate‑transform‑transfer” (BOTT) model, the centre now staffs about 1,000 people and operates as the bank’s largest hub, focused on outcome‑based, federated work that contributes directly to top‑line growth, product innovation, risk reduction and strategic goals. Leaders emphasize a shift from cost‑arbitrage to “capability sovereignty,” giving the GCC decision‑making rights, common standards, and governance, while moving all core banking applications to the cloud as a foundation for AI adoption with strong oversight. The Hyderabad team runs critical functions such as Citizens Pay (a buy‑now‑pay‑later service) and private‑banking capabilities, illustrating a blueprint for other banks to treat GCCs as strategic engineering assets rather than simple cost centers. Read more: https://timesofindia.indiatimes.com/technology/times-techies/cloud-first-ai-led-gcc-reimagines-global-banking/articleshow/131339817.cms #CitizensBank #Cognizant #HyderabadGCC #GCC #BOTTmodel
0
0
0
0
Replying to
(more Linux and FOSS news in previous posts of thread) Zed, the AI-native code editor from the creators of Atom, has finally reached version 1.0: https://alternativeto.net/news/2026/4/zed-the-ai-native-code-editor-from-the-creators-of-atom-has-finally-reached-version-1-0/ Notepad++ finally comes to Mac through a native fork with plugin support after 23 years: https://alternativeto.net/news/2026/4/notepad--finally-comes-to-mac-with-a-native-app-and-plugin-support-after-23-years/ Warp goes open-source for easier agentic development and introduces broader model support: https://alternativeto.net/news/2026/4/warp-goes-open-source-for-easier-agentic-development-and-introduces-broader-model-support/ GCC 16 debuts C++20 by default, adds Algol 68 and boosts diagnostics: https://alternativeto.net/news/2026/4/gcc-16-debuts-c-20-by-default-adds-algol-68-and-boosts-diagnostics/ FosseryWeb progress report: Java Stacks and Queues Cheatsheet now available, so all planned Java cheatsheets are done. Also added optional JS notice to the main cheatsheets page (code block copy buttons already required JS earlier, I just decided to be more transparent about it, even if blocking JS doesn't break the pages). https://fosseryweb.codeberg.page/@beta/cheatsheets/ https://fosseryweb-min.codeberg.page/@beta/cheatsheets/ I also added a Projects page (based on the XDG spec's new Projects directory lol, just kidding), to make my other projects easier to access. Not much there currently, just Burner Todo, and my Joplin config, but I might make a CLI version of Burner Todo later on (I'll learn C++ at university, will be a good practice project), and if I manage to switch from GNOME to a tiling WM, I'll also share my configs (although I'm not really a tinkerer type, I just like to set things up how I want and forget it). https://fosseryweb.codeberg.page/@beta/projects.html https://fosseryweb-min.codeberg.page/@beta/projects.html I also did some code refactoring, to unify the code of some page components (header, footer, Related contents section, etc.), for better consistency, readability; and I also shortened the names of some asset directories which were unnecessarily long. (more FOSS news in comments) #WeeklyNews #OpenSource #FOSSNews #OpenSourceNews #FOSS #News #Zed #NotepadPlusPlus #WarpTerminal #GCC #GCC16 #FosseryWebMin #FosseryWeb #Dev #Coding #Programming #Development #IDE #Terminal #AIDev #AIDevelopment #Compiler #Java #JavaCheatsheet #ProgrammingCheatsheet #FosseryTech
2
1
0
0
Replying to
@jperkin@federate.me.uk I'm not sure that this is the best fix. Since C++2011, there's been a template for std::log in that takes an integral type argument and so is the best match without ambiguity. https://cplusplus.com/reference/cmath/log/ vide libstdc++ https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=libstdc%2B%2B-v3/include/c_global/cmath;hb=HEAD#l322 and libc++ https://github.com/llvm/llvm-project/blob/main/libcxx/include/__math/logarithms.h#L35 Illumos's C++ support in isn't up to date with respect to C++ 2011 (unsurprisingly) and a fix that would actually improve and modernize the C++ support seems to be to add these templates for log and whatnot, in some fashion, with appropriate C++ version and type guards, to head/iso/math_iso.h where all of the other C++1998 overloads already are. That would remove ambiguity for both log(1) and std::log(1). #CPlusPlus #Illumos #gcc #clang
0
7
0
0
Replying to
@jperkin@federate.me.uk If I had an #Illumos system to do such work on, I probably could. Your patch is breaking the uniform way that the library is designed, over a whole load of headers. In this design, all of the overloads are declared inside namespace std in some iso/*_iso.h header, which headers like and and so forth then pull into the global namespace with using declarations. Ironically, it's a far more full-on C++ way of doing things because it's even declaring the C library functions in namespace std, but with "C" linkage. namespace std gets 1 "C" linkage overload and 2 "C++" linkage overloads for the various functions. #CPlusPlus #gcc #clang
0
5
0
0
Replying to
@jperkin@federate.me.uk Retaining that uniform, clean, system involves adding the stuff that's needed for more modern C++ anyway into the right iso/math_iso.h header. If I were doing that, head/iso/math_iso.h would gain something like template inline typename __illumos::__enable_if<__illumos::__is_integral<_T>::__value, double>::__type log(_T __v) { return log(static_cast(__v)); } inside namespace std, and #include at the top. There'd be an head/iso/type_traits.h with the well-known implementation of enable_if<> as __illumos::__enable_if<> and a suitable implementation of __illumos::__is_integral<> instantiated as appropriate. #CPlusPlus #gcc #clang #Illumos
0
3
0
0
Replying to
@jperkin@federate.me.uk All that said, the big question to answer is whether there is still in use an #Illumos C++ compiler that does not use either GNU libstdc++ or LLVM libc++. (Likely yes if a compiler bootstrap uses C++ before it has its own library built.) Because the inlined "C++" linkage stuff declared by the Illumos library has a fallback to other inline functions if using libstdc++ or libc++, the very easiest patch of all would seem to be just conditionally compile out (only) the extern "C++" {} block of head/iso/math_iso.h when either _LIBCPP_VERSION or __GLIBCXX__ is defined. That way, anything building with libstdc++ or libc++ doesn't get the Illumos "C++" linkage overloads as overloads in the global namespace, and only gets the 1 "C" linkage overload. #CPlusPlus #gcc #clang
0
2
0
0
Replying to
@jperkin@federate.me.uk You've missed two important bits. Your initial approach didn't test for _LIBCPP_VERSION or __GLIBCXX__. Your initial approach rather compiled all of this out except for one specific compiler. What I just described, in contrast, compiles everything in for all compilers except when libstdc++ or libc++ are used. It's library-sensitive, not compiler-sensitive. Because there's a stage at least in the GCC bootstrap where it is building itself with the pre-supplied compiler and library. In this mode, one does *not* want the #Illumos headers to have their C++ parts conditionally compiled out. One rather wants them to be fully natively functional the same as they are now. I also said *only* the extern "C++" {} block. Your initial approach went far beyond that and compiled out the declarations of a whole bunch of "C" linkage stuff. #CPlusPlus #gcc #clang
0
0
0
0
🟡 Drone Attack | 7/10 🇰🇼 🇮🇷 Iranian drones attack Kuwait Kuwait's army intercepted 28 Iranian drones targeting the country, with some hitting oil facilities and power plants, causing significant damage. The attacks occurred despite the announced ceasefire. 💬 SENTINEL: Продовження атак після оголошення перемир'я свідчить про складний процес доведення наказів до всіх підрозділів. #Kuwait #Iran #Drones #GCC
0
0
1
0