From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-pj1-f43.google.com (mail-pj1-f43.google.com [209.85.216.43]) by mx.groups.io with SMTP id smtpd.web12.1695.1659175284459542455 for ; Sat, 30 Jul 2022 03:01:24 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@gmail.com header.s=20210112 header.b=Rp1c8LuH; spf=pass (domain: gmail.com, ip: 209.85.216.43, mailfrom: ayushdevel1325@gmail.com) Received: by mail-pj1-f43.google.com with SMTP id x2-20020a17090ab00200b001f4da5cdc9cso456212pjq.0 for ; Sat, 30 Jul 2022 03:01:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:subject:from:cc:to:content-language :user-agent:mime-version:date:message-id:from:to:cc; bh=2kofvv//YY833gW/fHetiqahOTmFI3LR2i9QNRBNPiY=; b=Rp1c8LuHLLSreUJhJCo1MlFJXJklXhRcKBNwBizteWMLdpyHxTMWLKnd9sV5Blps1h oU2ISjz6uuPS+dlEAg5Ch9b8H37wXZv8tmzzpH9hCjWeOGSAQR3NNYwKnqwKyGHlMq2M 9OuLH/WQMpc8JB8Tq86aIQ/zidsK64WmiYdX4x7B3m5f9kXCH3RD4Ao9od9TkDGGLcfy pvIe37OPdrtMM2aU/uTVzdWpVpHM3vXGDG/lUovcEE5Osgz6H20hWdJG37C+Pq37njtH 00/1d/8EhLm3slFK3PwpaRcbofll1fQtOXfymJpMxfh4LFX8adpgjLqrMQ8tOiv1l1/g K3fQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:subject:from:cc:to:content-language :user-agent:mime-version:date:message-id:x-gm-message-state:from:to :cc; bh=2kofvv//YY833gW/fHetiqahOTmFI3LR2i9QNRBNPiY=; b=7naVSb+BpXaCKUdBV5oB0FvhT6mDis0s0x/opHz3DqubrhEmudFU/mcqIDBm4xPtXv Ox25uhBaDgM8vT9N6R3t7Yx1csLnibSr0O49i05BhLHbfVguNpK94MPvdLp/JnZTrmNl EKdOQFXHYyPQI+bEfBbrB3PAAhzZg0XlDg3IYmsOL9u0EovdiTo/6Cjf7rdCVWAC09rg Gbz8oV0slmjqUPhkvNjjRhoYECwqv+QneiXhDC21LGSZygZ4HNrn2fFk1CO2mllmroEs 3MD55SbkqzCDc6WorCLGlOBA3/0ZA0NykTuIdsHIVU+2amix2PrSh311K8NHDyDttQvn d6Vg== X-Gm-Message-State: ACgBeo2PRQTOYcuW/UevznwPGQDM0ojr+mJxywfU+agf80nkf9fvU0HE /QFF1I/RkLeLjYJA7unKRVBP9Bbf0AY= X-Google-Smtp-Source: AA6agR6OVsJ4eLtuLt9w8Q4yx0gi9E2SstLnFrPMMkQiO2oCc9Tin5PIzLk4Wemedh3fEk7vnHTaCA== X-Received: by 2002:a17:90b:78d:b0:1ef:c46f:19a7 with SMTP id l13-20020a17090b078d00b001efc46f19a7mr8456059pjz.216.1659175283446; Sat, 30 Jul 2022 03:01:23 -0700 (PDT) Return-Path: Received: from ?IPV6:2401:4900:1f3e:60eb:7d8e:f047:25a2:5a3a? ([2401:4900:1f3e:60eb:7d8e:f047:25a2:5a3a]) by smtp.gmail.com with ESMTPSA id bj19-20020a17090b089300b001f1acb6c3ebsm4464715pjb.34.2022.07.30.03.01.19 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 30 Jul 2022 03:01:22 -0700 (PDT) Message-ID: <69796452-56d6-75e9-a884-1c13fc68f8d6@gmail.com> Date: Sat, 30 Jul 2022 15:31:17 +0530 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0 To: "devel@edk2.groups.io" Cc: "Kinney, Michael D" , "mikuback@linux.microsoft.com" , "Gaibusab, Jabeena B" From: "Ayush Singh" Subject: Proposal to move Rust std work to edk2-staging Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hello everyone. The work on Rust std for UEFI has been progressing smoothly. Running Rust tests is now possible in it's entirety. The number of tests that fail is 133 (4 cause exception + 129 normal fails) out of 13,212 tests. Apart from the 4 tests that cause exceptions, most of the 129 other tests can be ignored since they are caused by needing dynamic linking and/or stack unwinding. So I think, it is time to start considering moving the project to a more appropriate repository before I open a PR upstream. However, I do have some concerns regarding moving to edk2-staging: 1. Rust development workflow does not use Mailing lists and Patches. This might create friction for the purely `rustc` developers who might want to submit changes and are accustomed to PRs. 2. Rust project does not seem to care about maintaining a clean history (most of the merges are performed by bots in form of roll-up merges). This is much different from how edk2 projects are usually managed. The reason where this becomes a problem is having to do re-bases. While Rust provides strong guarantees for stability of user facing APIs, the internal std APIs are constantly changing. Combine that with no clean-history and the upstream PR will probably have to be re-based on latest master every few weeks (and it will likely need manual intervention). I am planning on getting the code base ready for upstream PR before 15th August. The main things left to do is to publish new versions of `compiler_builtins` and `r-efi` crates, and refactor the code and UEFI documentation. Yours Sincerely Ayush Singh