Language Selection

English French German Italian Portuguese Spanish

Programming: Python, GCC, PHP and C++

Filed under
Development
  • PyCharm 2018.3.3
  • ARMv8.5 Branch Target Identification Support Lands In GCC 9 Compiler

    A late addition to the GCC 9 code compiler are new additions around ARMv8.5 as the latest revision to the AArch64 specification.

    Back in November saw initial ARMv8.5 commits for GCC9 while merging yesterday were more of the ARMv8.5 changes for squaring away this minor 64-bit ARM revision. The main addition yesterday was introducing Branch Target Identification (BTI). ARMv8.5's BTI has already been supported in LLVM/Clang and is part of ARM's Spectre Variant Two mitigations. Branch Target Identification when enabled marks valid targets of indirect branches and the CPU will trap an instruction in a protected page that is trying to perform an indirect branch to an instruction other than a marked BTI.

    Over the course of a few patches on Wednesday, that code is now in place for ARMv8 BTI with GCC 9.

  • PHP 7.3.1 Lands A Bunch Of Fixes For This Fastest PHP Release Yet

    For those that wait for a point release or two before upgrading to a new PHP release on your development box or web server, PHP 7.3.1 is out today as the first bug-fix release since last month's big PHP 7.3 release.

  • Fall 2018 ISO WG21 C++ Standards Committee meeting trip report

    The fall C++ meeting was held in San Diego, CA. As usual, Red Hat sent three of us to the meeting: myself from the Concurrency and Parallelism Study Group (SG1), Jason Merrill from the Core Language Working Group, and Jonathan Wakely from the Library Working Group (LEWG).

    SG1 had a fairly full plate but finished the week with a bit of breathing room to spare. This article describes the major topics discussed this week in SG1.

More in Tux Machines

Reducing sysadmin toil with Kubernetes controllers

Kubernetes is a platform for reducing toil cunningly disguised as a platform for running containers. The element that allows for both running containers and reducing toil is the Kubernetes concept of a Controller. [...] The canonical example of this in action is in how we manage Pods in Kubernetes. A Pod is effectively a running copy of an application that a specific worker node is asked to run. If that application crashes, the kubelet running on that node will start it again. However, if that node crashes, the Pod is not recovered, as the control loop (via the kubelet process) responsible for the resource no longer exists. To make applications more resilient, Kubernetes has the ReplicaSet controller. The ReplicaSet controller is bundled inside the Kubernetes controller-manager, which runs on the Kubernetes master node and contains the controllers for these more advanced resources. The ReplicaSet controller is responsible for ensuring that a set number of copies of your application is always running. To do this, the ReplicaSet controller requests that a given number of Pods is created. It then routinely checks that the correct number of Pods is still running and will request more Pods or destroy existing Pods to do so. By requesting a ReplicaSet from Kubernetes, you get a self-healing deployment of your application. You can further add lifecycle management to your workload by requesting a Deployment, which is a controller that manages ReplicaSets and provides rolling upgrades by managing multiple versions of your application's ReplicaSets. Read more

Android Leftovers

Server: IBM, LAMP and Kubernetes

  • A HATS For Many Occasions
    IBM gives customers plenty of options when it comes to its Rational Host Access Transformation software, including several modes of operation, different runtime options, and support for different operating systems in screen modernization engagements. With last week’s launch of HATS version 9.7, the development and deployment options got even wider. Regardless of which downstream options a HATS customer ultimately chooses, it all starts out basically the same on the front side of the sausage machine: Customers come to HATS because they have a 5250 (or 3270 or VT100) application that they want to transform, but they don’t want to go through the hassle, expense, and risk of modifying the IBM i, z/OS, or Unix application’s source code.
  • Six top skills that you should acquire in 2019
    There is a growing demand for the fullstack development skill set, which is the ability to develop tech both on the front-end/client side and back-end/server side. As you can’t learn all, select combinations like MEAN or LAMP stack.
  • Kubernetes and the Enterprise
    The reason we were having this conversation was around SUSE’s Cloud Application Platform (CAP). This is our Kubernetes focused Cloud Foundry distribution. And as part of the Kubernetes focus, we have been supporting and running SUSE CAP on Azure’s AKS for the last year or so. The conversation continued with observations that Kubernetes was clearly the future across IT. Yet to date, Cloud Foundry still has a good following with the large enterprise. And the thinking was that the Cloud Foundry approach really helped the large enteprise work with their applications, even if the applications were purely ‘container’ applications. Cloud Foundry makes the container-side of managing your ‘container’ application transparent. This approach ultimately lowers the tasks, breadth of tooling, and knowledge you have to surround Kubernetes with. It was with this thought, that a light-bulb went on.

today's howtos